Triple
T30527779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barking Riverside |
E776903
|
entity |
| Predicate | openedRailStation |
P68211
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Barking Riverside, openedRailStation, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedRailStation Context triple: [Barking Riverside, openedRailStation, 2022]
-
A.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
B.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
-
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.
openedAsTransitStation
chosen
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
E.
openedAsINDStation
Indicates that a location or facility began operation specifically as a station within the IND (Independent Subway System) network.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 8:17 p.m.