Triple
T3208850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sainte-Foy |
E67228
|
entity |
| Predicate | BritishSide |
P46194
|
FINISHED |
| Object | included British regulars and colonial troops |
—
|
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: included British regulars and colonial troops | Statement: [Battle of Sainte-Foy, BritishSide, included British regulars and colonial troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishSide Context triple: [Battle of Sainte-Foy, BritishSide, included British regulars and colonial troops]
-
A.
UKObjective
Indicates that an entity has the United Kingdom as its primary goal, target, or intended focus of action or effect.
-
B.
hasBritishAccent
Indicates that the subject speaks with a British accent.
-
C.
strength_British_side
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
-
D.
BritishForcesType
Indicates that an entity is classified as a type or category within the British armed forces.
-
E.
BritishAssociationsVotes
Indicates that the relationship involves votes cast or voting behavior within or by British associations.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa59888481908bdaefa1968d7f04 |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.