Triple
T24345918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Car Nicobar Airport |
E613637
|
entity |
| Predicate | remoteStatus |
P155799
|
FINISHED |
| Object | remote island airfield |
—
|
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: remote island airfield | Statement: [Car Nicobar Airport, remoteStatus, remote island airfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remoteStatus Context triple: [Car Nicobar Airport, remoteStatus, remote island airfield]
-
A.
locationStatus
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
B.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
C.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
D.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
-
E.
resourceStatus
Indicates the current condition or state of availability, usability, or operational readiness of a given resource.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:58 a.m.