Triple
T622011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander II of Scotland |
E14532
|
entity |
| Predicate | resolvedConflictIn |
P4546
|
FINISHED |
| Object | Galloway succession dispute |
—
|
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: Galloway succession dispute | Statement: [Alexander II of Scotland, resolvedConflictIn, Galloway succession dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvedConflictIn Context triple: [Alexander II of Scotland, resolvedConflictIn, Galloway succession dispute]
-
A.
endedConflict
chosen
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
-
C.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
D.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
E.
reasonForConflict
Indicates that one entity is the cause, motive, or underlying issue leading to a conflict involving another 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e402d9c8190936896e3ebb6edc5 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.