Triple
T5061804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannon Street station |
E114038
|
entity |
| Predicate | undergroundStationOpened |
P14462
|
FINISHED |
| Object | 1884 |
—
|
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: 1884 | Statement: [Cannon Street station, undergroundStationOpened, 1884]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundStationOpened Context triple: [Cannon Street station, undergroundStationOpened, 1884]
-
A.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
B.
railwayStationOpened
chosen
Indicates that a railway station began operation or was officially opened on a specified date or in a specified time period.
-
C.
openedAsRERStation
Indicates that a station began operation specifically as part of the RER (Réseau Express Régional) network from its opening date.
-
D.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
E.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74740ae08190930f1fd57187334e |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.