Triple
T25487602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne tram route 19 |
E638754
|
entity |
| Predicate | hasDirectionName |
P15156
|
FINISHED |
| Object | City |
—
|
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: City | Statement: [Melbourne tram route 19, hasDirectionName, City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionName Context triple: [Melbourne tram route 19, hasDirectionName, City]
-
A.
hasDirectionInName
Indicates that the entity’s name explicitly contains a directional term (e.g., north, south, east, west, or similar).
-
B.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
hasDirectionTitle
Indicates that an entity holds the role or position of director, as specified by a particular title.
-
D.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
E.
hasRouteDirection
chosen
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 2:33 p.m.