Triple
T5280707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laphroaig distillery |
E119488
|
entity |
| Predicate | royalWarrantGrantedIn |
P63835
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Laphroaig distillery, royalWarrantGrantedIn, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalWarrantGrantedIn Context triple: [Laphroaig distillery, royalWarrantGrantedIn, 1994]
-
A.
hasRoyalWarrantFrom
Indicates that one party has been formally granted a royal warrant or official endorsement by a specific royal person or household.
-
B.
grantedRoyalPatronageBy
Indicates that an individual, group, or institution has officially received support, endorsement, or sponsorship from a member of a royal family.
-
C.
monarchWhoGrantedTitle
Indicates the monarch who conferred or bestowed a particular title upon an individual.
-
D.
grantedRoyalPatentBy
Indicates that an entity has been formally given a royal patent by a specified royal authority or monarch.
-
E.
royalAssentGivenBy
Indicates that a formal approval or authorization, typically of legislation or an official act, is granted by a monarch or sovereign authority.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8c9b82ac819080e798713c0bb4d8 |
completed | March 20, 2026, 6:06 p.m. |
Created at: March 20, 2026, 1:52 p.m.