Triple
T3678522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCowan station |
E78053
|
entity |
| Predicate | lineTerminusType |
P9111
|
FINISHED |
| Object | terminal station |
—
|
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: terminal station | Statement: [McCowan station, lineTerminusType, terminal station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineTerminusType Context triple: [McCowan station, lineTerminusType, terminal station]
-
A.
lineTerminusFor
Indicates that one entity serves as an endpoint or terminus of a particular line or linear feature represented by another entity.
-
B.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
C.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
D.
requiresTerminatorAtEachEnd
Indicates that the related entity must have a terminator component installed or present at both of its ends.
-
E.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc46599188190a046eddb0d85c483 |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.