Triple
T27665688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Corbridge (918) |
E697220
|
entity |
| Predicate | hasBelligerentLeader |
P11563
|
FINISHED |
| Object | Constantine II of Scotland |
—
|
NE NERFINISHED |
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: Constantine II of Scotland | Statement: [Battle of Corbridge (918), hasBelligerentLeader, Constantine II of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBelligerentLeader Context triple: [Battle of Corbridge (918), hasBelligerentLeader, Constantine II of Scotland]
-
A.
belligerentLeader
chosen
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
-
B.
hasCountryLeader
Indicates that a specified country is led or governed by a particular leader (such as a president, prime minister, or monarch).
-
C.
hasAlliedLeader
Indicates that one entity serves as an allied leader or commander in relation to another entity.
-
D.
hadPrincipalLeader
Indicates that an entity was led or headed by a primary or chief leader.
-
E.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 2:38 p.m.