Triple
T28728517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX Corps, Army of the Potomac |
E730290
|
entity |
| Predicate | alsoServedWith |
P152828
|
FINISHED |
| Object | Army of the Ohio |
—
|
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 Ohio | Statement: [IX Corps, Army of the Potomac, alsoServedWith, Army of the Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoServedWith Context triple: [IX Corps, Army of the Potomac, alsoServedWith, Army of the Ohio]
-
A.
servedTogetherWith
chosen
Indicates that two entities were provided, offered, or used at the same time as part of the same service, event, or context.
-
B.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
C.
servesWith
Indicates that one entity is customarily presented, used, or consumed together with another as a complementary accompaniment.
-
D.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
E.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657662cec8190b1cf4ec832658a3b |
completed | May 2, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:57 a.m.