Triple
T19142893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leyes Fundamentales del Reino |
E468601
|
entity |
| Predicate | añoInicioVigencia |
P83226
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [Leyes Fundamentales del Reino, añoInicioVigencia, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: añoInicioVigencia Context triple: [Leyes Fundamentales del Reino, añoInicioVigencia, 1938]
-
A.
effectivePeriodStart
chosen
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
B.
contractStartYear
Indicates the calendar year in which a contract between parties officially begins.
-
C.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
D.
effectiveForAnnualPeriodsBeginningOnOrAfter
Indicates that something (such as a rule, standard, or requirement) applies starting from annual reporting periods whose first day is on or after a specified date.
-
E.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e976e340819098efccc30b2eef0e |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.