Triple
T31293766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholson’s |
E798016
|
entity |
| Predicate | alcoholLicence |
P162592
|
FINISHED |
| Object | on-licence |
—
|
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: on-licence | Statement: [Nicholson’s, alcoholLicence, on-licence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alcoholLicence Context triple: [Nicholson’s, alcoholLicence, on-licence]
-
A.
hasAlcoholLicense
chosen
Indicates that an entity possesses a valid authorization or permit to sell, serve, or distribute alcoholic beverages.
-
B.
licenceAuthority
Indicates that one entity has the official power or jurisdiction to grant, issue, or regulate licences for another entity or activity.
-
C.
drinkingPermitted
Indicates that consuming alcoholic beverages is allowed in a given context, location, or situation.
-
D.
alcoholPolicy
Indicates the rules or restrictions governing the possession, sale, or consumption of alcohol in a given context.
-
E.
regulatesAlcoholLevel
Indicates a relationship where one entity controls, adjusts, or maintains the alcohol level of another entity or system.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.