Triple
T27992331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron of Lochiel |
E706911
|
entity |
| Predicate | chieflyDesignation |
P162512
|
FINISHED |
| Object | Lochiel |
—
|
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: Lochiel | Statement: [Cameron of Lochiel, chieflyDesignation, Lochiel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chieflyDesignation Context triple: [Cameron of Lochiel, chieflyDesignation, Lochiel]
-
A.
initiallyDesignated
Indicates that an entity was assigned or specified in a particular role, state, or configuration at the beginning of a process or time period.
-
B.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
C.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
D.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
E.
isHighestDesignationOf
chosen
Indicates that one designation represents the topmost or most senior level within a defined hierarchy for a given entity or role.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:51 p.m.