Triple
T6304797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of York |
E141346
|
entity |
| Predicate | hasCapitalAttacked |
P63919
|
FINISHED |
| Object | York, capital of Upper Canada |
—
|
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: York, capital of Upper Canada | Statement: [Battle of York, hasCapitalAttacked, York, capital of Upper Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalAttacked Context triple: [Battle of York, hasCapitalAttacked, York, capital of Upper Canada]
-
A.
countryAttacked
Indicates that one country has carried out an attack against another country.
-
B.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
C.
cityAttackedBy
chosen
Indicates that a city is the target of an attack carried out by a specified agent or force.
-
D.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
E.
attemptedConquest
Indicates that one entity tried, but did not necessarily succeed, to conquer, subjugate, or take control of another entity.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645f26a881909d5746151c0843cc |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.