Triple
T27665678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Corbridge (918) |
E697220
|
entity |
| Predicate | involvesCombatant |
P21502
|
FINISHED |
| Object | Kingdom 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: Kingdom of Scotland | Statement: [Battle of Corbridge (918), involvesCombatant, Kingdom of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCombatant Context triple: [Battle of Corbridge (918), involvesCombatant, Kingdom of Scotland]
-
A.
combatantsIncluded
chosen
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
B.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
C.
combatantGovernment
Indicates that a government is a direct participant or party in a conflict, war, or combat situation.
-
D.
combatantsNationality
Indicates that the entities involved in a combat or conflict share or are associated with a specified nationality.
-
E.
sawCombatant
Indicates that one entity directly observed or witnessed another entity who is engaged as a combatant in a conflict or battle.
- 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_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 2:38 p.m.