Triple
T29555334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping Ongar Railway |
E749887
|
entity |
| Predicate | hasBusConnectionFrom |
P3791
|
FINISHED |
| Object | Epping Underground station |
—
|
NE NERFINISHED |
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: Epping Underground station | Statement: [Epping Ongar Railway, hasBusConnectionFrom, Epping Underground station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusConnectionFrom Context triple: [Epping Ongar Railway, hasBusConnectionFrom, Epping Underground station]
-
A.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
C.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
D.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
E.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 5:15 p.m.