Triple
T8656120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Graham, 4th Earl of Menteith |
E205419
|
entity |
| Predicate | heldPowerIn |
P29191
|
FINISHED |
| Object | central Highlands 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: central Highlands of Scotland | Statement: [John Graham, 4th Earl of Menteith, heldPowerIn, central Highlands of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldPowerIn Context triple: [John Graham, 4th Earl of Menteith, heldPowerIn, central Highlands of Scotland]
-
A.
heldTemporalPower
chosen
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
B.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
C.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4844586081909b687e278496eefa |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.