Triple
T24531381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nueva Island |
E606818
|
entity |
| Predicate | involvedInDispute |
P26178
|
FINISHED |
| Object | Beagle Channel arbitration |
—
|
NE NERFINISHED |
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: Beagle Channel arbitration | Statement: [Nueva Island, involvedInDispute, Beagle Channel arbitration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedInDispute Context triple: [Nueva Island, involvedInDispute, Beagle Channel arbitration]
-
A.
disputeInvolves
chosen
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
B.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
C.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
D.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
E.
significantDispute
Indicates a serious, often prolonged disagreement or conflict exists between the involved entities.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.