Triple
T7949487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milano Cadorna station |
E184577
|
entity |
| Predicate | hasRoleInCityNetwork |
P33918
|
FINISHED |
| Object | central interchange node |
—
|
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: central interchange node | Statement: [Milano Cadorna station, hasRoleInCityNetwork, central interchange node]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInCityNetwork Context triple: [Milano Cadorna station, hasRoleInCityNetwork, central interchange node]
-
A.
hasRoleInNetwork
chosen
Indicates that an entity holds a specific functional position or responsibility within a particular network.
-
B.
hasRoleInCommunity
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
C.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
D.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
E.
hasComponentCity
Indicates that an entity includes or is composed of one or more cities as its constituent parts.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2d09a4819097aa49e29a5426ec |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:10 p.m.