Triple
T38401074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English invasion of Scotland (1296) |
E900900
|
entity |
| Predicate | hasScottishCommander |
P148537
|
FINISHED |
| Object | John Balliol |
—
|
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: John Balliol | Statement: [English invasion of Scotland (1296), hasScottishCommander, John Balliol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScottishCommander Context triple: [English invasion of Scotland (1296), hasScottishCommander, John Balliol]
-
A.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
B.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
C.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
D.
notableCommanderOf
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
E.
notableCommanderNationality
chosen
Indicates that the notable commander associated with an entity has the specified nationality.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:31 p.m.