Triple
T7029637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cachar district |
E163236
|
entity |
| Predicate | hasAirport |
P105
|
FINISHED |
| Object | Silchar Airport |
E34709
|
NE 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: Silchar Airport | Statement: [Cachar district, hasAirport, Silchar Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Silchar Airport Context triple: [Cachar district, hasAirport, Silchar Airport]
-
A.
Silchar Airport
chosen
Silchar Airport is a domestic airport serving the city of Silchar and the Barak Valley region in the Indian state of Assam.
-
B.
Jorhat Airport
Jorhat Airport is a domestic airport in Assam, India, serving the city of Jorhat and surrounding regions with regional air connectivity.
-
C.
Dibrugarh Airport
Dibrugarh Airport is a domestic airport in the Indian state of Assam that serves the city of Dibrugarh and the surrounding Upper Assam region.
-
D.
Tezpur Airport
Tezpur Airport is a domestic airport in Tezpur, Assam, India, serving as a regional air transport hub for the surrounding area.
-
E.
Dimapur Airport
Dimapur Airport is a domestic airport in Nagaland, India, serving as the primary air gateway to the state capital, Kohima, and surrounding regions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e20dbc8c8190a7446290747d8078 |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7943ca8548190877d2698265ce7da |
completed | March 28, 2026, 8:41 a.m. |
Created at: March 27, 2026, 2:35 p.m.