Triple
T28927718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STOXX Europe 600 |
E733695
|
entity |
| Predicate | hasReviewFrequency |
P56962
|
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, hasReviewFrequency, quarterly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReviewFrequency Context triple: [STOXX Europe 600, hasReviewFrequency, quarterly]
-
A.
hasReviewPeriod
Indicates that an entity is associated with a specific time span during which it is subject to review or evaluation.
-
B.
areReviewedEvery
chosen
Indicates that one entity conducts reviews of another entity at every specified time interval or on every relevant occasion.
-
C.
hasBeenReviewedIn
Indicates that an entity has been evaluated or critiqued within a specific review, publication, or reviewing context.
-
D.
hasReviewReception
Indicates that an entity has received a critical or evaluative review describing how it was received or perceived.
-
E.
hasReviewed
Indicates that one entity has examined, evaluated, or provided feedback on another entity (such as a work, product, or performance).
- 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_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: April 28, 2026, 8:25 a.m.