Triple
T10488054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Place (former terminus) |
E247341
|
entity |
| Predicate | replacedAsTerminusBy |
P63485
|
FINISHED |
| Object | Newhaven branch terminus |
—
|
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: Newhaven branch terminus | Statement: [York Place (former terminus), replacedAsTerminusBy, Newhaven branch terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAsTerminusBy Context triple: [York Place (former terminus), replacedAsTerminusBy, Newhaven branch terminus]
-
A.
formerTerminusFor
Indicates that a location once served as the endpoint or final stop of a route, line, or service, but no longer holds that status.
-
B.
successorTerminus
chosen
Indicates that one terminus directly follows another in a defined sequence or progression.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
terminusFrom
Indicates that something serves as the endpoint or final destination from which a route, path, or connection originates.
-
E.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5096b609c81909e23fd8fb6426f4a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.