Triple
T23996754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beacon Cay |
E605210
|
entity |
| Predicate | sovereigntyDisputed |
P15542
|
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: [Beacon Cay, sovereigntyDisputed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereigntyDisputed Context triple: [Beacon Cay, sovereigntyDisputed, true]
-
A.
sovereigntyChallenged
Indicates that an entity’s authority or control over its territory, people, or decisions is being questioned, disputed, or undermined by another party or circumstance.
-
B.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
C.
locatedInDisputedTerritory
chosen
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
-
D.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
E.
islandContested
Indicates that control or ownership of an island is disputed or contested between two or more parties.
- F. None of above.
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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38f8a208190a293c64b9c9202c0 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:38 p.m.