Triple
T16433152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain of the Honourable Corps of Gentlemen-at-Arms |
E399116
|
entity |
| Predicate | bodyguardType |
P122763
|
FINISHED |
| Object | mounted bodyguard |
—
|
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: mounted bodyguard | Statement: [Captain of the Honourable Corps of Gentlemen-at-Arms, bodyguardType, mounted bodyguard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyguardType Context triple: [Captain of the Honourable Corps of Gentlemen-at-Arms, bodyguardType, mounted bodyguard]
-
A.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
B.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
protectsProductType
Indicates that one entity provides protection or safeguarding specifically for a certain type or category of product.
-
D.
wearerType
Indicates the type or category of entity that is intended to wear or use the associated item.
-
E.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
- F. None of above. chosen
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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9f2e8c81909c60b8fb78255e5f |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.