Triple
T25896113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Stedman area |
E652473
|
entity |
| Predicate | battleOutcomeCommemorated |
P4717
|
FINISHED |
| Object | Union defensive victory |
—
|
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: Union defensive victory | Statement: [Fort Stedman area, battleOutcomeCommemorated, Union defensive victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOutcomeCommemorated Context triple: [Fort Stedman area, battleOutcomeCommemorated, Union defensive victory]
-
A.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
-
B.
regionOfBattlesCommemorated
Indicates the geographic region where the battles being commemorated took place.
-
C.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
D.
notableBattleRecognized
Indicates that a particular battle is formally acknowledged or recognized as notable in relation to the subject.
-
E.
commemoratedIn
chosen
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6038411088190975af82ad1156963 |
completed | May 2, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:23 a.m.