Triple
T25486633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Provost of Edinburgh |
E638727
|
entity |
| Predicate | hasAdditionalRole |
P161
|
FINISHED |
| Object | Lord-Lieutenant of the City of Edinburgh |
E1233958
|
NE 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: Lord-Lieutenant of the City of Edinburgh | Statement: [Lord Provost of Edinburgh, hasAdditionalRole, Lord-Lieutenant of the City of Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalRole Context triple: [Lord Provost of Edinburgh, hasAdditionalRole, Lord-Lieutenant of the City of Edinburgh]
-
A.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
B.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
D.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- F. None of above.
Provenance (4 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77d26488190898b7befa111282b |
completed | May 2, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ad69bdb4819084e8a5dce44ce2e0 |
completed | May 22, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:32 p.m.