Triple
T38295923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Decree 2964/1981 |
E1022485
|
entity |
| Predicate | numberWithinYear |
—
|
GENERATED |
| Object | 2964 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberWithinYear Context triple: [Royal Decree 2964/1981, numberWithinYear, 2964]
-
A.
dayInYear
Indicates that a specific day occurs within a particular year.
-
B.
yearType
Indicates the classification or category assigned to a specific year (e.g., academic, fiscal, calendar, leap).
-
C.
startDateInYear
Indicates that an entity’s start date occurs within a specified calendar year.
-
D.
positionInCivilYear
Indicates the specific point or ordering of something within the sequence of time units that make up a civil (calendar) year.
-
E.
yearRound
Indicates that the relationship, condition, or activity holds continuously throughout the entire year without seasonal interruption.
- F. None of above. chosen
Provenance (1 batch)
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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.