Triple
T2833054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory Monument |
E62284
|
entity |
| Predicate | isMajorTrafficHub |
P37527
|
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: [Victory Monument, isMajorTrafficHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTrafficHub Context triple: [Victory Monument, isMajorTrafficHub, true]
-
A.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
B.
isMajorTransportLinkIn
Indicates that a transport route or connection serves as a primary or significant transportation link within a specified area or region.
-
C.
isMajorHubType
chosen
Indicates that an entity functions as a primary or central hub within a larger network or system.
-
D.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
E.
isTransportationHubCodeFor
Indicates that a given code uniquely identifies and represents a specific transportation hub, such as a station, airport, or terminal.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec036dc8190bc2d974f6d82eda9 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.