Triple
T34704441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agra–Jaipur route |
E1000461
|
entity |
| Predicate | connectsWithOtherRouteAt |
P155912
|
FINISHED |
| Object | Achhnera 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: Achhnera Junction | Statement: [Agra–Jaipur route, connectsWithOtherRouteAt, Achhnera Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithOtherRouteAt Context triple: [Agra–Jaipur route, connectsWithOtherRouteAt, Achhnera Junction]
-
A.
connectedRoute
chosen
Indicates that there is a direct or logically continuous path linking two locations or segments within a network.
-
B.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
isContiguousWithAnyRoute
Indicates that an entity shares at least one continuous boundary or segment with any existing route.
-
E.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 3, 2026, 3:59 p.m.