Triple
T28927717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STOXX Europe 600 |
E733695
|
entity |
| Predicate | isRebalanced |
P24422
|
FINISHED |
| Object | quarterly |
—
|
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: quarterly | Statement: [STOXX Europe 600, isRebalanced, quarterly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRebalanced Context triple: [STOXX Europe 600, isRebalanced, quarterly]
-
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.
isReclaimed
Indicates that something previously used, degraded, or discarded has been restored, recovered, or converted back into a usable or improved state.
-
C.
isBalanced
Indicates that the elements or parts involved are in a state of equilibrium, with no side or component outweighing or dominating the others.
-
D.
requiresBalancing
Indicates that one entity or action depends on being offset, equalized, or counteracted by another to maintain a required equilibrium or fairness.
-
E.
isReclaimedFrom
Indicates that something has been recovered, restored, or taken back from a previous state, owner, or condition.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b4fee008190bc43ed7e719872db |
completed | May 2, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:25 a.m.