Triple
T12247525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cornfield |
E291886
|
entity |
| Predicate | partOfLargerAction |
P4074
|
FINISHED |
| Object | morning phase of the Battle of Antietam |
—
|
LITERAL FINISHED |
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: morning phase of the Battle of Antietam | Statement: [The Cornfield, partOfLargerAction, morning phase of the Battle of Antietam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLargerAction Context triple: [The Cornfield, partOfLargerAction, morning phase of the Battle of Antietam]
-
A.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
B.
partOfSeriesOfEvents
chosen
Indicates that an event is one element within a larger, ordered sequence of related events.
-
C.
partOfMission
Indicates that one entity is a component, phase, or element belonging to or included within a larger mission.
-
D.
partOfCampaign
Indicates that an entity participates in, belongs to, or is included within a specific campaign.
-
E.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.