Triple
T28590513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby Line–Stanstead border crossing |
E723625
|
entity |
| Predicate | borderLinePassesThrough |
P108342
|
FINISHED |
| Object | residential properties |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: residential properties | Statement: [Derby Line–Stanstead border crossing, borderLinePassesThrough, residential properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLinePassesThrough Context triple: [Derby Line–Stanstead border crossing, borderLinePassesThrough, residential properties]
-
A.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
B.
passesThroughPoint
Indicates that a path, line, or trajectory intersects or goes through a specific point in space.
-
C.
hasBorderThrough
chosen
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
D.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
E.
borderIsAffectedBy
Indicates that a border’s state, condition, or characteristics are influenced or changed by another factor or event.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 4:20 a.m.