Triple
T14452060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangra Airport |
E358360
|
entity |
| Predicate | isCivilEnclave |
P114333
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Kangra Airport, isCivilEnclave, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCivilEnclave Context triple: [Kangra Airport, isCivilEnclave, no]
-
A.
notableEnclave
Indicates that one place is a distinct, noteworthy enclave located within or surrounded by another area or community.
-
B.
isCivilFlag
Indicates that the flag is used for civil purposes, typically by private citizens or non-military, non-governmental entities.
-
C.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
D.
isCivilTownship
Indicates that one entity is a civil township, i.e., an administrative or local government subdivision, in relation to another entity.
-
E.
containsEnclave
Indicates that one region or territory fully surrounds and encloses another distinct region or territory as an enclave.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:19 a.m.