Triple
T10659701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of White Oak Swamp |
E251190
|
entity |
| Predicate | primaryAction |
P80144
|
FINISHED |
| Object | artillery duel at the swamp crossing |
—
|
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: artillery duel at the swamp crossing | Statement: [Battle of White Oak Swamp, primaryAction, artillery duel at the swamp crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAction Context triple: [Battle of White Oak Swamp, primaryAction, artillery duel at the swamp crossing]
-
A.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
B.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primaryInteraction
chosen
Indicates the main or most significant interaction occurring between the involved entities.
-
D.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
E.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e0174dc4819093e577993c65ed32 |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:07 p.m.