Triple
T18183501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Alford |
E435349
|
entity |
| Predicate | covenanterForcesIncluded |
P65659
|
FINISHED |
| Object | Lowland infantry |
—
|
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: Lowland infantry | Statement: [Battle of Alford, covenanterForcesIncluded, Lowland infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenanterForcesIncluded Context triple: [Battle of Alford, covenanterForcesIncluded, Lowland infantry]
-
A.
CovenanterForcesIncluded
chosen
Indicates that the forces involved included or comprised Covenanter troops or military units.
-
B.
CovenanterPoliticalAlignment
Indicates the political stance or affiliation associated with a Covenanter in relation to contemporary political factions, policies, or conflicts.
-
C.
royalistForcesIncluded
Indicates that the composition of the royalist forces included the specified entity or group.
-
D.
strengthCovenanters
Indicates that one entity possesses, provides, or is associated with the strength or power of the Covenanters in relation to another entity.
-
E.
CovenanterObjective
Indicates that an entity has the role or status of a covenanter whose purpose or goal is directed toward a specified objective.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffd0abc81908cc07d28bdc3d48f |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.