Triple
T37175270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSE/JSE Africa Index Series |
E921021
|
entity |
| Predicate | methodologyProvider |
P164975
|
FINISHED |
| Object | FTSE Russell |
—
|
NE NERFINISHED |
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: FTSE Russell | Statement: [FTSE/JSE Africa Index Series, methodologyProvider, FTSE Russell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodologyProvider Context triple: [FTSE/JSE Africa Index Series, methodologyProvider, FTSE Russell]
-
A.
hasMethodologyProvider
chosen
Indicates that one entity serves as the provider or source of the methodology used or applied by another entity.
-
B.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
C.
methodologyName
Indicates the specific named method or procedure used or referenced in performing an action or study.
-
D.
hasMethodologyFeature
Indicates that something possesses or is characterized by a particular methodological attribute, technique, or feature.
-
E.
describesMethodology
Indicates that one entity explains, specifies, or characterizes the methodology or procedure used by 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.