Triple
T15755037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSEMIB |
E381945
|
entity |
| Predicate | isTradableViaFutures |
P117739
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FTSEMIB, isTradableViaFutures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTradableViaFutures Context triple: [FTSEMIB, isTradableViaFutures, true]
-
A.
isOptionsTraded
Indicates that options contracts based on the referenced entity are actively traded in a financial market.
-
B.
usesFuturesContractType
chosen
Indicates that one entity employs or is associated with a specific type of futures contract in its activities or relationships.
-
C.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
-
D.
isElectronicTradingEligible
Indicates that an entity meets the required conditions to participate in or be processed through electronic trading.
-
E.
typeOfTrading
Indicates a relationship where one entity specifies the kind or category of trading activity associated with another 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05031f6a08190bfb333eced0a59a1 |
completed | April 16, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.