Triple
T5699824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kilsyth (1645) |
E125630
|
entity |
| Predicate | CovenanterStrengthApproximate |
P36039
|
FINISHED |
| Object | around 6,000–7,000 men |
—
|
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: around 6,000–7,000 men | Statement: [Battle of Kilsyth (1645), CovenanterStrengthApproximate, around 6,000–7,000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CovenanterStrengthApproximate Context triple: [Battle of Kilsyth (1645), CovenanterStrengthApproximate, around 6,000–7,000 men]
-
A.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
B.
commandingForce2Strength
chosen
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
C.
commandingForce1Strength
Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
-
D.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
E.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0241030408190be774a5d2ca6e999 |
completed | March 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.