Triple
T15755063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSEMIB |
E381945
|
entity |
| Predicate | isUsedInIndexFunds |
P120207
|
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, isUsedInIndexFunds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInIndexFunds Context triple: [FTSEMIB, isUsedInIndexFunds, true]
-
A.
isIndexFund
Indicates that an investment fund is structured to track a specific market index rather than actively selecting individual securities.
-
B.
isBenchmarkETF
Indicates that an exchange-traded fund (ETF) serves as a benchmark or reference standard against which other investments or funds are compared.
-
C.
isUsedForDerivatives
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
-
D.
isUCITS
Indicates that an investment fund complies with the UCITS (Undertakings for Collective Investment in Transferable Securities) regulatory framework.
-
E.
isTotalMarketIndex
Indicates that the referenced financial instrument or dataset represents a total market index covering a broad or complete segment of a market rather than a subset.
- 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_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. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.