Triple
T34330211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savage’s Station on the Richmond and York River Railroad |
E880981
|
entity |
| Predicate | armyServed |
P126571
|
FINISHED |
| Object | Army of the Potomac |
—
|
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: Army of the Potomac | Statement: [Savage’s Station on the Richmond and York River Railroad, armyServed, Army of the Potomac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armyServed Context triple: [Savage’s Station on the Richmond and York River Railroad, armyServed, Army of the Potomac]
-
A.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
B.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
C.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
D.
servedArmy
chosen
Indicates that an entity has performed military service in, or been a member of, a particular army.
-
E.
countryOfMilitaryService
Indicates that an entity served or is serving in the armed forces of a specified country.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.