Triple
T21196934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah State Legislature |
E522349
|
entity |
| Predicate | generalSessionLength |
P12499
|
FINISHED |
| Object | 45 calendar 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: 45 calendar days | Statement: [Utah State Legislature, generalSessionLength, 45 calendar days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalSessionLength Context triple: [Utah State Legislature, generalSessionLength, 45 calendar days]
-
A.
sessionLength
chosen
Indicates the duration of time that a particular session lasts from start to end.
-
B.
durationPerParticipant
Indicates the amount of time associated with or allocated to each individual participant in the related activity or event.
-
C.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333c9bac8190a203802a8b8e4143 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.