Triple

T13515410
Position Surface form Disambiguated ID Type / Status
Subject United Nations Security Council Resolution 706 E322746 entity
Predicate monetaryCap P84602 FINISHED
Object 1600000000 United States dollars 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: 1600000000 United States dollars | Statement: [United Nations Security Council Resolution 706, monetaryCap, 1600000000 United States dollars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: monetaryCap
Context triple: [United Nations Security Council Resolution 706, monetaryCap, 1600000000 United States dollars]
  • A. fundingCapType
    Indicates the classification or category of a limit placed on the amount of funding that can be provided.
  • B. hasMaximumBalanceLimit chosen
    Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
  • C. incomeLimit
    Indicates a specified maximum income threshold that must not be exceeded for a condition, eligibility, or rule to apply.
  • D. monetaryComponent
    Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
  • E. deficitLimit
    Indicates a constraint or maximum allowable amount on how large a deficit (shortfall or negative balance) may be.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafa0ed508190b2855171b1945e84 completed April 12, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69dbae0b63748190b5e207f84b2532ea completed April 12, 2026, 2:36 p.m.
Created at: April 9, 2026, 9:44 p.m.