Triple
T1074006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Indian Ocean Territory |
E23391
|
entity |
| Predicate | hasDisputedStatus |
P23974
|
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: [British Indian Ocean Territory, hasDisputedStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputedStatus Context triple: [British Indian Ocean Territory, hasDisputedStatus, true]
-
A.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
B.
hasDisputeHistory
Indicates that there has been at least one prior dispute or conflict involving the related entities.
-
C.
hasDisputedIdentityWith
Indicates that two entities are associated with conflicting, uncertain, or contested identifications, such that their true or correct identities are in dispute relative to each other.
-
D.
handlesDisputesOver
Indicates that one entity is responsible for managing, resolving, or adjudicating disputes concerning another entity.
-
E.
hasDebatedStatus
Indicates that an entity has participated in or been assigned a particular status related to a debate or debating activity.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92cbfd481909e2f928c1d06ebaa |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8d5076481908640a0d873efdf14 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.