Triple
T9309786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alkire-Foster method |
E223977
|
entity |
| Predicate | coreIndex |
P88001
|
FINISHED |
| Object | M0 (adjusted headcount ratio) |
—
|
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: M0 (adjusted headcount ratio) | Statement: [Alkire-Foster method, coreIndex, M0 (adjusted headcount ratio)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreIndex Context triple: [Alkire-Foster method, coreIndex, M0 (adjusted headcount ratio)]
-
A.
keyIndex
Indicates the position or numerical index assigned to a specific key within an ordered set or collection of keys.
-
B.
corePosition
Indicates that one entity occupies the central or primary position within another entity or structure.
-
C.
mainIndex
Indicates that one entity serves as the primary or central index or reference point for another entity within a structured system.
-
D.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
E.
indexStructure
Indicates that one entity serves as an index or organizational framework that structures, arranges, or provides access to another entity or set of entities.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ac17488190aa6acf7a61420632 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.