Triple
T15841285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMX Stockholm 30 |
E384106
|
entity |
| Predicate | rebalancingMonths |
P24422
|
FINISHED |
| Object | January |
—
|
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: January | Statement: [OMX Stockholm 30, rebalancingMonths, January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebalancingMonths Context triple: [OMX Stockholm 30, rebalancingMonths, January]
-
A.
hasRebalancing
chosen
Indicates that an entity undergoes or is subject to an adjustment process to restore a desired balance or allocation among its components or related elements.
-
B.
restatementPeriod
Indicates the time span over which something is restated, revised, or reissued, typically referring to a defined interval covered by a correction or updated version.
-
C.
rebuildPeriod
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
D.
usualMonthHeld
Indicates the month in which an event or activity is typically or customarily held.
-
E.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e764088190afba6c5c1acf8199 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.