Triple
T28731665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Valverde |
E730675
|
entity |
| Predicate | stateOriginOfConfederateForces |
P187376
|
FINISHED |
| Object | Texas |
—
|
NE NERFINISHED |
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: Texas | Statement: [Battle of Valverde, stateOriginOfConfederateForces, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOriginOfConfederateForces Context triple: [Battle of Valverde, stateOriginOfConfederateForces, Texas]
-
A.
joinedConfederateStatesOfAmerica
Indicates that an entity became a member of, or formally aligned itself with, the Confederate States of America.
-
B.
stateEnteredByConfederates
Indicates that a particular state or region was entered or invaded by Confederate forces.
-
C.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
D.
confederateForcesType
Indicates the type or classification of confederate forces involved in a given military or conflict-related context.
-
E.
includesFormerConfederateStates
Indicates that the subject set or grouping contains one or more states that were part of the former Confederate States of America.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 28, 2026, 5:58 a.m.