Triple
T4432153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 114th United States Congress |
E95354
|
entity |
| Predicate | adjournedSineDie |
P55969
|
FINISHED |
| Object | 2017-01-03 |
—
|
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: 2017-01-03 | Statement: [114th United States Congress, adjournedSineDie, 2017-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjournedSineDie Context triple: [114th United States Congress, adjournedSineDie, 2017-01-03]
-
A.
adjournedFor
Indicates that an event, meeting, or proceeding has been paused or suspended for a specified duration or until a particular time or condition is met.
-
B.
laterCourt
Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
-
C.
courtOrdered
Indicates that an action, condition, or relationship exists because it has been formally mandated or imposed by a court order.
-
D.
appealDate
Indicates the date on which an appeal is formally filed, recorded, or scheduled in relation to a decision or case.
-
E.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
- F. None of above. chosen
Provenance (4 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556cd83881908547aa311c4f17fa |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:31 p.m.