Triple
T33072181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London |
E846261
|
entity |
| Predicate | hasMajorRailTerminus |
P1071
|
FINISHED |
| Object | Waterloo 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: Waterloo station | Statement: [London, hasMajorRailTerminus, Waterloo station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRailTerminus Context triple: [London, hasMajorRailTerminus, Waterloo station]
-
A.
hasMajorRailwayStation
chosen
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
B.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
-
C.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
D.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
E.
hasMajorRailCorridor
Indicates that a location or region is traversed by a primary, high-capacity railway route used for significant passenger or freight transport.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: May 1, 2026, 1:25 a.m.