Triple
T29114705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Vyner |
E737010
|
entity |
| Predicate | royalService |
P104507
|
FINISHED |
| Object | goldsmith to the royal household |
—
|
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: goldsmith to the royal household | Statement: [Thomas Vyner, royalService, goldsmith to the royal household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalService Context triple: [Thomas Vyner, royalService, goldsmith to the royal household]
-
A.
royalFunction
Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
-
B.
royalUse
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
C.
serviceToMonarch
chosen
Indicates a relationship where one entity provides service, duty, or assistance to a monarch or sovereign ruler.
-
D.
royalDuties
Indicates that an entity has responsibilities, obligations, or functions associated with a royal role or position.
-
E.
postRoyalUse
Indicates that something is used or occurs after a royal event, status, or period has ended.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:21 a.m.