Triple
T16545386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeoman Bed Hanger |
E401927
|
entity |
| Predicate | isRoleWithin |
P161
|
FINISHED |
| Object | bodyguard of the British monarch |
—
|
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: bodyguard of the British monarch | Statement: [Yeoman Bed Hanger, isRoleWithin, bodyguard of the British monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRoleWithin Context triple: [Yeoman Bed Hanger, isRoleWithin, bodyguard of the British monarch]
-
A.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
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.
roleInPath
Indicates that an entity participates in a specific path or route by occupying a particular role or position within that path.
-
D.
isAuthorityFor
Indicates that one entity holds recognized power, control, or decision-making responsibility over another entity or domain.
-
E.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34562c30c81908d6318f359002ff2 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.