Triple
T14130146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Quebec (1760) |
E340140
|
entity |
| Predicate | foughtAfter |
P112918
|
FINISHED |
| Object | British capture of Quebec in 1759 |
—
|
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: British capture of Quebec in 1759 | Statement: [Battle of Quebec (1760), foughtAfter, British capture of Quebec in 1759]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtAfter Context triple: [Battle of Quebec (1760), foughtAfter, British capture of Quebec in 1759]
-
A.
fought
Indicates that one entity engaged in physical or armed conflict or combat against another entity.
-
B.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
C.
hasFight
Indicates that one entity engages in a physical or verbal conflict with another entity.
-
D.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
E.
feudedWith
Indicates a prolonged, often hostile conflict or rivalry between two entities.
- F. None of above. chosen
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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:23 p.m.