Triple
T15090433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Glenlivet |
E360399
|
entity |
| Predicate | largerForceDefeated |
P117275
|
FINISHED |
| Object | Protestant army |
—
|
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: Protestant army | Statement: [Battle of Glenlivet, largerForceDefeated, Protestant army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largerForceDefeated Context triple: [Battle of Glenlivet, largerForceDefeated, Protestant army]
-
A.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
B.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
C.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
D.
locationOfMajorDefeat
Indicates the place where a significant or decisive defeat of a party occurred.
-
E.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:04 a.m.