Triple
T27096487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raid on Ogdensburg |
E686316
|
entity |
| Predicate | defendingForceOrigin |
P166913
|
FINISHED |
| Object | United 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: United States | Statement: [Raid on Ogdensburg, defendingForceOrigin, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendingForceOrigin Context triple: [Raid on Ogdensburg, defendingForceOrigin, United States]
-
A.
defenderBase
Indicates that one entity serves as the primary defensive location or stronghold associated with another entity.
-
B.
combatantsOrigin
chosen
Indicates the place or source from which the participants in a conflict or fight originate.
-
C.
patriotForcesOrigin
Indicates that the origin or source location of a group of patriot forces is being specified.
-
D.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
-
E.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:44 a.m.