Triple
T30995549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bases Orgánicas de la República Mexicana de 1843 |
E789786
|
entity |
| Predicate | períodoDeVigencia |
P33304
|
FINISHED |
| Object | década de 1840 |
—
|
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: década de 1840 | Statement: [Bases Orgánicas de la República Mexicana de 1843, períodoDeVigencia, década de 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: períodoDeVigencia Context triple: [Bases Orgánicas de la República Mexicana de 1843, períodoDeVigencia, década de 1840]
-
A.
validityPeriodEnd
Indicates the date and time at which a previously valid state, authorization, or condition ceases to be valid.
-
B.
hasValidityPeriod
chosen
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
C.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
D.
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.
-
E.
licensingPeriod
Indicates the time span during which a license is valid and its associated rights are legally in effect.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:56 p.m.