Triple
T5150146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Texas Infantry |
E116172
|
entity |
| Predicate | sideInTheCivilWar |
P58454
|
FINISHED |
| Object | Confederate |
—
|
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: Confederate | Statement: [1st Texas Infantry, sideInTheCivilWar, Confederate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInTheCivilWar Context triple: [1st Texas Infantry, sideInTheCivilWar, Confederate]
-
A.
memberSupportedSideInCivilWar
chosen
Indicates that a member or group actively backed, aligned with, or provided support to a particular side or faction in a civil war.
-
B.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
C.
opponentInAmericanCivilWar
Indicates that two entities were on opposing sides in the American Civil War.
-
D.
unionArmy
Indicates that an entity served in, was part of, or is otherwise affiliated with the Union Army (the United States Army of the North) during the American Civil War.
-
E.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.