Triple
T27497334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jolarpettai–Shoranur line |
E694051
|
entity |
| Predicate | importantJunctionOnRoute |
P148844
|
FINISHED |
| Object | Erode Junction |
—
|
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: Erode Junction | Statement: [Jolarpettai–Shoranur line, importantJunctionOnRoute, Erode Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantJunctionOnRoute Context triple: [Jolarpettai–Shoranur line, importantJunctionOnRoute, Erode Junction]
-
A.
importantJunctionTown
Indicates that a town functions as a key junction point where major routes, lines, or pathways intersect or connect.
-
B.
significantJunction
chosen
Indicates a junction or intersection that plays an important or central role in connecting routes or pathways.
-
C.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
D.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
E.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 1:09 p.m.