Triple
T10134147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTAS.L |
E226812
|
entity |
| Predicate | isIndexFund |
P92458
|
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: [FTAS.L, isIndexFund, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndexFund Context triple: [FTAS.L, isIndexFund, true]
-
A.
isBenchmarkETF
Indicates that an exchange-traded fund (ETF) serves as a benchmark or reference standard against which other investments or funds are compared.
-
B.
isBlueChipIndex
Indicates that an index is composed primarily of large, well-established, financially stable companies considered blue-chip stocks.
-
C.
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.
-
D.
hasSubFund
Indicates that an entity (typically a fund) includes or controls another fund as a subordinate or component fund within its structure.
-
E.
isUCITS
Indicates that an investment fund complies with the UCITS (Undertakings for Collective Investment in Transferable Securities) regulatory framework.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd33808048190b6023a6cd83fc179 |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:06 p.m.