Triple
T28728550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX Corps, Army of the Potomac |
E730290
|
entity |
| Predicate | includedUnitsFrom |
P199264
|
FINISHED |
| Object | New England states |
—
|
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: New England states | Statement: [IX Corps, Army of the Potomac, includedUnitsFrom, New England states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedUnitsFrom Context triple: [IX Corps, Army of the Potomac, includedUnitsFrom, New England states]
-
A.
someUnits
Indicates that one entity is associated with an unspecified or non-zero quantity of units of another entity.
-
B.
listedUnit
Indicates that an entity is specified or recorded as a particular unit in a list or catalog.
-
C.
hasUnitsFrom
Indicates that one entity derives, adopts, or uses its measurement units from another specified source entity.
-
D.
basedUnitsInclude
Indicates that a composite or derived unit is defined using, and therefore includes, the specified base unit(s) in its construction.
-
E.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
- F. None of above. chosen
Provenance (4 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_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: April 28, 2026, 5:57 a.m.