Triple
T13861208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBEX 35 |
E333199
|
entity |
| Predicate | adjustsFor |
P112148
|
FINISHED |
| Object | corporate actions |
—
|
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: corporate actions | Statement: [IBEX 35, adjustsFor, corporate actions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjustsFor Context triple: [IBEX 35, adjustsFor, corporate actions]
-
A.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
B.
notAdjustedFor
Indicates that a value, measure, or result has not been modified or corrected to account for certain factors, conditions, or variables.
-
C.
adaptsFrom
Indicates that one entity is derived, modified, or transformed from another, preserving core elements while changing form, medium, or context.
-
D.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_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. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:14 p.m.