Triple
T22008944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian/Chagos |
E543523
|
entity |
| Predicate | usedByMilitaryInstallations |
P146261
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Indian/Chagos, usedByMilitaryInstallations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByMilitaryInstallations Context triple: [Indian/Chagos, usedByMilitaryInstallations, true]
-
A.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
B.
isMilitaryInstallation
Indicates that a location functions as a military facility or base used for defense, training, operations, or related armed forces activities.
-
C.
hostsMilitaryInstallation
Indicates that a location contains or accommodates a military base, facility, or installation operated by armed forces.
-
D.
hasFormerMilitaryInstallationNearby
Indicates that an entity is located close to a site where a military installation previously existed but is no longer active.
-
E.
militaryInstallationType
Indicates the specific category or kind of military installation associated with an entity (e.g., base, fort, airfield, naval station).
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a376048190a78ba7efd303b58a |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:21 p.m.