Triple

T594307
Position Surface form Disambiguated ID Type / Status
Subject Eurodollar futures E17345 entity
Predicate typicalContractSize P3664 FINISHED
Object 1,000,000 U.S. dollars notional 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: 1,000,000 U.S. dollars notional | Statement: [Eurodollar futures, typicalContractSize, 1,000,000 U.S. dollars notional]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalContractSize
Context triple: [Eurodollar futures, typicalContractSize, 1,000,000 U.S. dollars notional]
  • A. hasLotSize
    Indicates that an entity possesses a specific amount or extent of physical area, typically referring to the size of a parcel of land or property lot.
  • B. typicalUnitSize chosen
    Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
  • C. tradeInstrument
    Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
  • D. typeOfContract
    Indicates the specific kind or category of contractual agreement that applies between the related entities.
  • E. typicalCapacity
    Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49bd15c5881909b59ed4c88687e7b completed March 1, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69a494ceeb7881909a91ed1a35d5bf0a completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.