Triple
T36933424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenancy system of Scotland |
E913545
|
entity |
| Predicate | deputyOfficeHolderTitle |
P3256
|
FINISHED |
| Object | Vice Lord-Lieutenant |
—
|
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: Vice Lord-Lieutenant | Statement: [Lieutenancy system of Scotland, deputyOfficeHolderTitle, Vice Lord-Lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deputyOfficeHolderTitle Context triple: [Lieutenancy system of Scotland, deputyOfficeHolderTitle, Vice Lord-Lieutenant]
-
A.
deputyExecutiveHeadTitle
Indicates the official job title held by a person serving as the deputy to an organization's executive head.
-
B.
hasDeputyLeaderTitle
chosen
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
C.
deputyOf
Indicates that one entity serves as the subordinate or second-in-command to another, acting with delegated authority on their behalf.
-
D.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
E.
currentOfficeHolderTitle
Indicates the official title or position name held by the person who currently occupies a given office 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdf2dc148190bca1bf6bca2e6732 |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.