Triple
T25229254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne tram route 64 |
E632177
|
entity |
| Predicate | hasCityCentreTerminus |
P15947
|
FINISHED |
| Object | Melbourne central city |
—
|
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: Melbourne central city | Statement: [Melbourne tram route 64, hasCityCentreTerminus, Melbourne central city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityCentreTerminus Context triple: [Melbourne tram route 64, hasCityCentreTerminus, Melbourne central city]
-
A.
hasMetroTerminus
Indicates that one location serves as the terminal (end) station of a metro line for another location.
-
B.
hasCapitalTerminus
Indicates that a transportation route or line has its endpoint located in a capital city.
-
C.
isCityCentreStop
chosen
Indicates that a stop is located within or serves the central area of a city.
-
D.
isMainBusStationFor
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
E.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 1:04 p.m.