Triple
T24993373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maastricht criteria |
E625503
|
entity |
| Predicate | hasReferencePeriod |
P4343
|
FINISHED |
| Object | usually the previous year for fiscal data |
—
|
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: usually the previous year for fiscal data | Statement: [Maastricht criteria, hasReferencePeriod, usually the previous year for fiscal data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferencePeriod Context triple: [Maastricht criteria, hasReferencePeriod, usually the previous year for fiscal data]
-
A.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
B.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
C.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
E.
hasReviewPeriod
Indicates that an entity is associated with a specific time span during which it is subject to review or evaluation.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 18, 2026, 6:04 a.m.