Triple
T27534317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Greater London |
E695056
|
entity |
| Predicate | confersTitleOnOfficeHolder |
P3622
|
FINISHED |
| Object | High Sheriff of Greater London |
—
|
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: High Sheriff of Greater London | Statement: [High Sheriff of Greater London, confersTitleOnOfficeHolder, High Sheriff of Greater London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confersTitleOnOfficeHolder Context triple: [High Sheriff of Greater London, confersTitleOnOfficeHolder, High Sheriff of Greater London]
-
A.
confersTitle
chosen
Indicates that one entity grants or bestows an official title or designation upon another entity.
-
B.
confersOfficeOn
Indicates that one entity formally grants or bestows an official position or office upon another entity.
-
C.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
D.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
E.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 1:28 p.m.