Triple
T1025380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund of Scotland |
E22127
|
entity |
| Predicate | contested |
P5850
|
FINISHED |
| Object | throne of Scotland |
—
|
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: throne of Scotland | Statement: [Edmund of Scotland, contested, throne of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contested Context triple: [Edmund of Scotland, contested, throne of Scotland]
-
A.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
B.
titleContested
chosen
Indicates that the legitimacy or ownership of a title is disputed between parties.
-
C.
officeContested
Indicates that a particular office or position is being actively sought or challenged by multiple parties in an election or selection process.
-
D.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
E.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b72619cc8190932fdfa0c74dc055 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.