Triple
T13861212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBEX 35 |
E333199
|
entity |
| Predicate | hasConstituentSelectionCriterion |
P136
|
FINISHED |
| Object | trading volume |
—
|
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: trading volume | Statement: [IBEX 35, hasConstituentSelectionCriterion, trading volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstituentSelectionCriterion Context triple: [IBEX 35, hasConstituentSelectionCriterion, trading volume]
-
A.
hasSubcriterion
Indicates that a criterion includes another, more specific criterion as a subordinate part of its evaluation structure.
-
B.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
C.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
D.
hasMemberCriteria
Indicates that a group, collection, or set is defined or constrained by specific criteria that its members must satisfy.
-
E.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:14 p.m.