Triple
T4342487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ^DJI |
E97814
|
entity |
| Predicate | indexWeightingScheme |
P35293
|
FINISHED |
| Object | price weighting |
—
|
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: price weighting | Statement: [^DJI, indexWeightingScheme, price weighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexWeightingScheme Context triple: [^DJI, indexWeightingScheme, price weighting]
-
A.
weightingMethod
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
-
B.
weightingFunction
chosen
Indicates a function that assigns relative importance or influence (weights) to elements within a set, often to adjust their impact in a calculation or decision process.
-
C.
associatedIndexWeightEntity
Indicates a relationship where an index is linked to a specific weight entity that quantifies or influences its value or behavior.
-
D.
sectorWeighting
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
-
E.
indexType
Indicates the classification or category of an index associated with an entity or 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351878c148190b384053479d41caf |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.