Triple
T25896095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Stedman area |
E652473
|
entity |
| Predicate | commemoratesCommander |
P161243
|
FINISHED |
| Object | Ulysses S. Grant |
—
|
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: Ulysses S. Grant | Statement: [Fort Stedman area, commemoratesCommander, Ulysses S. Grant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesCommander Context triple: [Fort Stedman area, commemoratesCommander, Ulysses S. Grant]
-
A.
commemoratesCommander
chosen
Indicates that one entity serves to honor or remember a specific military commander.
-
B.
commemoratesUnit
Indicates that one entity serves as a memorial or tribute recognizing, honoring, or remembering a specific unit.
-
C.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
E.
eraCommemorated
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 8:23 a.m.