Triple
T28050160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikkei 225 |
E708797
|
entity |
| Predicate | hasFuturesContracts |
P165117
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nikkei 225, hasFuturesContracts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFuturesContracts Context triple: [Nikkei 225, hasFuturesContracts, yes]
-
A.
usesFuturesContractType
Indicates that one entity employs or is associated with a specific type of futures contract in its activities or relationships.
-
B.
hasUnderlyingAssets
Indicates that one entity is supported, backed, or derived from another entity or set of entities that serve as its foundational assets.
-
C.
hasContractWith
Indicates that one entity is bound by a formal contract or agreement with another entity.
-
D.
isUsedForDerivatives
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
-
E.
hasDealingsIn
Indicates that an entity engages in activities, transactions, or business related to a particular domain, location, or subject.
- F. None of above. chosen
Provenance (4 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 8:32 p.m.