Triple
T9032371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zunheboto |
E216401
|
entity |
| Predicate | roadDistanceToKohima |
P85788
|
FINISHED |
| Object | approximately 150–200 kilometers |
—
|
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: approximately 150–200 kilometers | Statement: [Zunheboto, roadDistanceToKohima, approximately 150–200 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDistanceToKohima Context triple: [Zunheboto, roadDistanceToKohima, approximately 150–200 kilometers]
-
A.
distanceFromGuwahati_km
Indicates the physical distance, measured in kilometers, between an entity and the location of Guwahati.
-
B.
distanceFromShillong
Indicates the spatial distance between a given entity or location and Shillong.
-
C.
distanceToDelhiByRoad_km
Indicates the road travel distance, measured in kilometers, from a given place to Delhi.
-
D.
distanceToSiliguri_km
Indicates the physical distance, measured in kilometers, between a given location and Siliguri.
-
E.
distanceToSrinagar_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Srinagar.
- F. None of above. chosen
Provenance (4 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa0c89c81909792190f08fef8df |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.