Triple

T6607745
Position Surface form Disambiguated ID Type / Status
Subject Beagle conflict E149159 entity
Predicate arbitrationOutcome P2931 FINISHED
Object award largely in favor of Chile 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: award largely in favor of Chile | Statement: [Beagle conflict, arbitrationOutcome, award largely in favor of Chile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: arbitrationOutcome
Context triple: [Beagle conflict, arbitrationOutcome, award largely in favor of Chile]
  • A. agreementOutcome
    Indicates the result or consequence that follows from reaching or failing to reach an agreement between parties.
  • B. legalOutcome chosen
    Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
  • C. divisionArbitratedBy
    Indicates that the resolution or allocation of a division (e.g., of assets, responsibilities, or territory) is determined or settled by a specified arbitrating party or authority.
  • D. hasArbitrationAwardDate
    Indicates the date on which an arbitration award was formally issued or became effective.
  • E. outcomeOf
    Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cf3796d08190a26e988386089447 completed March 27, 2026, 6:40 p.m.
PD Predicate disambiguation batch_69c6acfed25481909cac74c84a9fe088 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:57 p.m.