Triple
T19142892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leyes Fundamentales del Reino |
E468601
|
entity |
| Predicate | periodoVigencia |
P33304
|
FINISHED |
| Object | 1938-1977 |
—
|
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-1977 | Statement: [Leyes Fundamentales del Reino, periodoVigencia, 1938-1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodoVigencia Context triple: [Leyes Fundamentales del Reino, periodoVigencia, 1938-1977]
-
A.
hasValidityPeriod
chosen
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
B.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
C.
validityRegime
Indicates the set of conditions, rules, or context under which something (such as a statement, document, or status) is considered valid or in force.
-
D.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
E.
policyPeriod
Indicates the time span during which a particular policy is in effect or valid.
- 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.