Triple
T2750632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1864 United States presidential election |
E60976
|
entity |
| Predicate | statesCarriedByGeorgeBMcClellan |
P41629
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1864 United States presidential election, statesCarriedByGeorgeBMcClellan, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statesCarriedByGeorgeBMcClellan Context triple: [1864 United States presidential election, statesCarriedByGeorgeBMcClellan, 3]
-
A.
commandingUnionArmy
Indicates that one entity holds the role or responsibility of leading and directing the Union Army.
-
B.
joinedConfederateStatesOfAmerica
Indicates that an entity became a member of, or formally aligned itself with, the Confederate States of America.
-
C.
statesCarriedByWinner
Indicates that the specified states were carried (won) by the winning candidate in an election.
-
D.
notableCommanderAmerican
Indicates that the subject served as a notable military commander who is American.
-
E.
confederateArmyComponent
Indicates that one entity functions as a constituent unit, formation, or subpart of the Confederate army.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6b6f0c8190901ab032dfb21e37 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd91497ec8190927e91ad33549eda |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:56 p.m.