Triple
T22686906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 52nd United States Congress |
E560940
|
entity |
| Predicate | adjournedIn |
P88451
|
FINISHED |
| Object | 1893 |
—
|
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: 1893 | Statement: [52nd United States Congress, adjournedIn, 1893]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjournedIn Context triple: [52nd United States Congress, adjournedIn, 1893]
-
A.
adjournsIn
chosen
Indicates that an event, meeting, or session formally ends or is suspended within a specified location or context.
-
B.
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.
-
C.
adjournedSineDie
Indicates that a meeting, session, or proceeding has been adjourned without setting a date or time to reconvene.
-
D.
canAdjourn
Indicates that an entity has the authority or ability to formally end, suspend, or postpone a meeting, session, or proceeding.
-
E.
extendedInCourt
Indicates that a legal deadline, order, or proceeding has been formally prolonged or continued through a court decision or action.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178649aac8190a9d41f5d82895bdf |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.