Triple
T227061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamber of Deputies of Mexico |
E4334
|
entity |
| Predicate | currentLegislatureTermLength |
P540
|
FINISHED |
| Object | 3 years |
—
|
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: 3 years | Statement: [Chamber of Deputies of Mexico, currentLegislatureTermLength, 3 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLegislatureTermLength Context triple: [Chamber of Deputies of Mexico, currentLegislatureTermLength, 3 years]
-
A.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
legislativeTermNumber
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
C.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
D.
legislativePeriodicity
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
-
E.
legislativeSession
Indicates that an entity is a formal meeting period of a legislative body during which it conducts its official business, such as debating and passing laws.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.