Triple
T27904032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Corps (Union Army) |
E705718
|
entity |
| Predicate | garrisonOrCamp |
P28243
|
FINISHED |
| Object | Camp near Falmouth, Virginia |
—
|
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: Camp near Falmouth, Virginia | Statement: [III Corps (Union Army), garrisonOrCamp, Camp near Falmouth, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonOrCamp Context triple: [III Corps (Union Army), garrisonOrCamp, Camp near Falmouth, Virginia]
-
A.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
B.
garrisonOrMobilizationPoint
Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
-
C.
garrisonOrTheater
Indicates that one entity serves as a military garrison or theater of operations for another entity.
-
D.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
E.
garrisonedForce
chosen
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:44 p.m.