Triple
T11258925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSE/JSE Africa All Share Index |
E266509
|
entity |
| Predicate | isTotalReturnVariantAvailable |
P98768
|
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: [FTSE/JSE Africa All Share Index, isTotalReturnVariantAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTotalReturnVariantAvailable Context triple: [FTSE/JSE Africa All Share Index, isTotalReturnVariantAvailable, true]
-
A.
isTotalReturnIndex
Indicates that the index value reflects total return, including both price changes and reinvested income such as dividends or interest.
-
B.
hasReturnVariant
Indicates that an entity has an associated alternative form or version specifically used for returning or sending back.
-
C.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
E.
isPriceIndexVariantAvailable
Indicates whether an alternative or variant of a given price index is available.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e936cb048190b4d6fb2851ef8932 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.