Triple
T18609839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico House of Representatives |
E454860
|
entity |
| Predicate | oddNumberedYearSessionLength |
P12499
|
FINISHED |
| Object | 60 days |
—
|
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: 60 days | Statement: [New Mexico House of Representatives, oddNumberedYearSessionLength, 60 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oddNumberedYearSessionLength Context triple: [New Mexico House of Representatives, oddNumberedYearSessionLength, 60 days]
-
A.
hasSeasonLength
Indicates that one entity has a specified duration or length for its season.
-
B.
sessionLength
chosen
Indicates the duration of time that a particular session lasts from start to end.
-
C.
minimumSessionsPerYear
Indicates the smallest number of sessions that must occur within a one-year period.
-
D.
maximumDurationOfParliamentSessionPerYear
Indicates the longest allowable length of time that a parliament is permitted to be in session within a single year.
-
E.
hasLegislativeSessionCount
Indicates the number of legislative sessions associated with a given legislative body, term, or jurisdiction.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d0048b08190a7dd407f14d95799 |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.