Triple

T29581346
Position Surface form Disambiguated ID Type / Status
Subject Ecuadorian–Peruvian territorial disputes E753594 entity
Predicate finalSettlementDate P82025 FINISHED
Object 26 October 1998 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: 26 October 1998 | Statement: [Ecuadorian–Peruvian territorial disputes, finalSettlementDate, 26 October 1998]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: finalSettlementDate
Context triple: [Ecuadorian–Peruvian territorial disputes, finalSettlementDate, 26 October 1998]
  • A. settledDate
    Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
  • B. dateFinalized chosen
    Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
  • C. finalDeliveryDate
    Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
  • D. associatedSettlementPeriod
    Indicates a temporal period during which a particular settlement is or was occupied, active, or otherwise relevant.
  • E. settlementPeriod
    Indicates the length of time between a transaction or agreement and its final settlement or completion.
  • 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_69f0ef80bf8c8190ad286e99f7df0c63 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69fce7671f108190bf3ebf54339068b5 completed May 7, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69fce5b5a84c81908ac1b5b9f08d48d0 completed May 7, 2026, 7:19 p.m.
Created at: April 28, 2026, 6:07 p.m.