Triple
T28050161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikkei 225 |
E708797
|
entity |
| Predicate | hasOptionsContracts |
P71615
|
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, hasOptionsContracts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOptionsContracts Context triple: [Nikkei 225, hasOptionsContracts, yes]
-
A.
isOptionsTraded
chosen
Indicates that options contracts based on the referenced entity are actively traded in a financial market.
-
B.
hasFuturesContracts
Indicates that one party holds or is engaged in futures contracts related to another entity, asset, or underlying reference.
-
C.
hasOptionsSymbol
Indicates that a financial instrument is associated with a tradable options contract identified by a specific options symbol.
-
D.
optionMoneyness
Indicates the relationship between an option’s strike price and the current price of its underlying asset (e.g., whether the option is in, at, or out of the money).
-
E.
hasFuturesExchange
Indicates that there exists a futures exchange associated with, operated by, or relevant to the referenced entity.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 8:32 p.m.