Triple
T22396994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Croydon |
E553660
|
entity |
| Predicate | isMajorCommuterHub |
P145586
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East Croydon, isMajorCommuterHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorCommuterHub Context triple: [East Croydon, isMajorCommuterHub, true]
-
A.
isCommuterHub
Indicates that a location functions as a central node where many commuters start, end, or transfer during their regular travel.
-
B.
isMajorTransitNode
chosen
Indicates that a location functions as a primary hub in a transportation network, where multiple major routes or services intersect or connect.
-
C.
hasMajorHubIn
Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
-
D.
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.
-
E.
isMajorHubType
Indicates that an entity functions as a primary or central hub within a larger network or system.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585f67108190b8d3f23eaa0ed120 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.