Triple
T2450222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 41st United States Congress |
E53684
|
entity |
| Predicate | dealtWith |
P17506
|
FINISHED |
| Object | readmission of former Confederate states |
—
|
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: readmission of former Confederate states | Statement: [41st United States Congress, dealtWith, readmission of former Confederate states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dealtWith Context triple: [41st United States Congress, dealtWith, readmission of former Confederate states]
-
A.
dealtWithEvent
chosen
Indicates that an entity has handled, responded to, or otherwise taken action to address a particular event.
-
B.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
C.
correspondedWith
Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
-
D.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
E.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.