Triple
T25407204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloody Angle |
E636590
|
entity |
| Predicate | startOfMajorAction |
P87911
|
FINISHED |
| Object | dawn, May 12, 1864 |
—
|
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: dawn, May 12, 1864 | Statement: [Bloody Angle, startOfMajorAction, dawn, May 12, 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfMajorAction Context triple: [Bloody Angle, startOfMajorAction, dawn, May 12, 1864]
-
A.
startOfMajorCampaign
Indicates that the referenced event marks the beginning of a significant, large-scale campaign or operation.
-
B.
durationOfMajorAction
Indicates the length of time over which a primary or significant action takes place.
-
C.
initialAction
chosen
Indicates the first or starting action taken in a sequence of actions or events.
-
D.
startedActingOn
Indicates that one entity has begun to perform, execute, or apply an action, influence, or process upon another entity.
-
E.
significantStartEvent
Indicates that an event marks an important or defining beginning point for a process, state, or relationship.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 1:52 p.m.