Triple
T26304672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Byland |
E661647
|
entity |
| Predicate | primaryOpponentOfEngland |
P192671
|
FINISHED |
| Object | Robert the Bruce |
—
|
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: Robert the Bruce | Statement: [Battle of Byland, primaryOpponentOfEngland, Robert the Bruce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpponentOfEngland Context triple: [Battle of Byland, primaryOpponentOfEngland, Robert the Bruce]
-
A.
keyInternationalOpponent
Indicates that one entity is a primary or significant adversary or rival of another in an international context.
-
B.
RyderCupOpponent
Indicates that two entities are opposing teams or competitors facing each other in a Ryder Cup golf match or event.
-
C.
mainCompetitorNation
chosen
Indicates that one nation is the primary rival or chief competing nation of another.
-
D.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
E.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 26, 2026, 10:18 p.m.