Triple

T1445343
Position Surface form Disambiguated ID Type / Status
Subject Oil Spill Liability Trust Fund E31163 entity
Predicate subLimitRemovalCostsUSD P99 FINISHED
Object 500000000 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: 500000000 | Statement: [Oil Spill Liability Trust Fund, subLimitRemovalCostsUSD, 500000000]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subLimitRemovalCostsUSD
Context triple: [Oil Spill Liability Trust Fund, subLimitRemovalCostsUSD, 500000000]
  • A. reducedCostOf
    Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
  • B. smallCaseDollarLimit
    Indicates a constraint or maximum allowable amount of money expressed in small-denomination (lower-value) dollar units.
  • C. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • D. coversCosts
    Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
  • E. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69a4991633388190a4d61b5a98aa407a completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c55714588190a95b4f677c21cbaa completed March 1, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69a4c47a840c819083307a65c027a19e completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8 p.m.