Triple
T9507102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 57th United States Congress |
E229296
|
entity |
| Predicate | adjournsIn |
P88451
|
FINISHED |
| Object | 1903 |
—
|
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: 1903 | Statement: [57th United States Congress, adjournsIn, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjournsIn Context triple: [57th United States Congress, adjournsIn, 1903]
-
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.
canAdjourn
Indicates that an entity has the authority or ability to formally end, suspend, or postpone a meeting, session, or proceeding.
-
C.
adjournedSineDie
Indicates that a meeting, session, or proceeding has been adjourned without setting a date or time to reconvene.
-
D.
concludes
Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
-
E.
laterCourt
Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98543b1881908b537abdc1d2f9c0 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:57 p.m.