Triple
T27096486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raid on Ogdensburg |
E686316
|
entity |
| Predicate | attackingForceOrigin |
P150760
|
FINISHED |
| Object | Upper Canada |
E9414
|
NE 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: Upper Canada | Statement: [Raid on Ogdensburg, attackingForceOrigin, Upper Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackingForceOrigin Context triple: [Raid on Ogdensburg, attackingForceOrigin, Upper Canada]
-
A.
attackingAircraftOrigin
Indicates that one entity is the place or source from which an attacking aircraft originates.
-
B.
attackingForceApprox
Indicates that one entity is the approximate attacking force, in terms of size or strength, relative to another entity or context.
-
C.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
D.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
-
E.
countryOfOriginOfAttackers
chosen
Indicates the country from which the attackers originated or are associated in the context of an attack.
- F. None of above.
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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623b1d8b48190ae71d57f60d2e327 |
completed | May 2, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1248054fd481909b8acca7826f4c2e |
completed | May 24, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:44 a.m.