Triple
T26690883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highway network of Karnataka |
E672875
|
entity |
| Predicate | linksToState |
P115309
|
FINISHED |
| Object | Maharashtra |
—
|
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: Maharashtra | Statement: [National Highway network of Karnataka, linksToState, Maharashtra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksToState Context triple: [National Highway network of Karnataka, linksToState, Maharashtra]
-
A.
connectsStates
chosen
Indicates a relationship where one entity serves as a link or route that joins two or more states together.
-
B.
navigationLinkedTo
Indicates that one element is connected to another as a navigational target or destination, enabling movement or access between them.
-
C.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
D.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
E.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 3:26 a.m.