Triple
T27648184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1000V |
E696768
|
entity |
| Predicate | associatedIndexProvider |
P155397
|
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: [R1000V, associatedIndexProvider, FTSE Russell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedIndexProvider Context triple: [R1000V, associatedIndexProvider, FTSE Russell]
-
A.
associatedIndex
Indicates that one entity is linked to another through a corresponding index or positional reference.
-
B.
indexProvider
Indicates that one entity serves as a provider or source of an index (such as a listing, catalog, or reference structure) that can be used by another entity.
-
C.
hasIndexProvider
chosen
Indicates that an entity is associated with or uses a specific index provider responsible for supplying indexing capabilities or services.
-
D.
associatedIndexWeightEntity
Indicates a relationship where an index is linked to a specific weight entity that quantifies or influences its value or behavior.
-
E.
knownCompositeForIndex
Indicates that a given value is recognized as a composite number corresponding to a particular index in a sequence or data structure.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
Created at: April 27, 2026, 2:30 p.m.