Triple
T595649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CME Ether futures |
E17375
|
entity |
| Predicate | contractStandardization |
P7508
|
FINISHED |
| Object | standardized contract specifications |
—
|
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: standardized contract specifications | Statement: [CME Ether futures, contractStandardization, standardized contract specifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractStandardization Context triple: [CME Ether futures, contractStandardization, standardized contract specifications]
-
A.
standardizationApproach
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
-
B.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
C.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
D.
standardizedIn
chosen
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
E.
industryStandardFor
Indicates that something is widely accepted or recognized as the conventional or benchmark practice, specification, or norm within a particular industry.
- 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_69a49bd280ac8190b6a530ce73da85c8 |
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.