Triple
T1731444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euro Stoxx 50 |
E37818
|
entity |
| Predicate | hasReturnVariant |
P31824
|
FINISHED |
| Object | price index |
—
|
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 index | Statement: [Euro Stoxx 50, hasReturnVariant, price index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReturnVariant Context triple: [Euro Stoxx 50, hasReturnVariant, price index]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
C.
hasVariance
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
-
D.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
E.
hasVarianceSymbol
Indicates that one entity is associated with, or represented by, a specific variance symbol in a mathematical or statistical context.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab5c54362881908895ab249cad8c1d |
completed | March 6, 2026, 10:59 p.m. |
Created at: March 4, 2026, 7:30 p.m.