Triple
T4801107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley de Sucesión en la Jefatura del Estado |
E106832
|
entity |
| Predicate | vigenciaHasta |
P33304
|
FINISHED |
| Object | 1978-12-29 |
—
|
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: 1978-12-29 | Statement: [Ley de Sucesión en la Jefatura del Estado, vigenciaHasta, 1978-12-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vigenciaHasta Context triple: [Ley de Sucesión en la Jefatura del Estado, vigenciaHasta, 1978-12-29]
-
A.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
B.
hasValidityPeriod
chosen
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
C.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
D.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
E.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.