Triple
T1266479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 85th United States Congress |
E15611
|
entity |
| Predicate | adjournsOn |
P7175
|
FINISHED |
| Object | 1959-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: 1959-01-03 | Statement: [85th United States Congress, adjournsOn, 1959-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjournsOn Context triple: [85th United States Congress, adjournsOn, 1959-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.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
-
C.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
D.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
E.
endsOn
chosen
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c037f14c8190baa42f70f8846583 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.