Triple
T9028934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSE All-World Index |
E216118
|
entity |
| Predicate | numberOfConstituentsApproximate |
P5741
|
FINISHED |
| Object | around 4000 |
—
|
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: around 4000 | Statement: [FTSE All-World Index, numberOfConstituentsApproximate, around 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfConstituentsApproximate Context triple: [FTSE All-World Index, numberOfConstituentsApproximate, around 4000]
-
A.
numberOfConstituents
chosen
Indicates the total count of individual components or members that make up a larger whole or group.
-
B.
previousNumberOfConstituents
Indicates the number of constituents an entity had at an earlier point in time, before its current state.
-
C.
estimatedConstituencySize
Indicates the approximate number of individuals or units that are believed to fall within a particular constituency or represented group.
-
D.
hasNumberOfConstituencies
Indicates the specific count of constituencies associated with an entity.
-
E.
representedConstituentsFrom
Indicates that an entity served as a representative or proxy for certain constituents originating from another entity or source.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.