Triple
T25498235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chennai–Tirupati route |
E639036
|
entity |
| Predicate | hasDirectionFromChennai |
P49386
|
FINISHED |
| Object | northwest |
—
|
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: northwest | Statement: [Chennai–Tirupati route, hasDirectionFromChennai, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionFromChennai Context triple: [Chennai–Tirupati route, hasDirectionFromChennai, northwest]
-
A.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
B.
travelsDirection
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
C.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
-
D.
directionFromColombo
Indicates the cardinal or relative compass direction of an entity’s location measured from Colombo.
-
E.
hasDirectionFrom
chosen
Indicates that one entity has a specific orientation or directional relationship when referenced from another entity.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 2:41 p.m.