Triple
T17351731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Rappahannock Station |
E421828
|
entity |
| Predicate | ConfederatePrisonersTaken |
P65452
|
FINISHED |
| Object | over 1,600 |
—
|
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: over 1,600 | Statement: [Battle of Rappahannock Station, ConfederatePrisonersTaken, over 1,600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ConfederatePrisonersTaken Context triple: [Battle of Rappahannock Station, ConfederatePrisonersTaken, over 1,600]
-
A.
confederatePrisonersTaken
chosen
Indicates that one party has captured and taken prisoners who are affiliated with or fighting for the Confederate side.
-
B.
UnionPrisonersTaken
Indicates that Union forces captured and held individuals as prisoners.
-
C.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
D.
captivesTaken
Indicates that one entity has taken another entity or group into captivity, holding them against their will.
-
E.
prisonersOfWar
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2ca0708190aae8306ec3a6f2a7 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.