Triple
T25617640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table Table |
E642200
|
entity |
| Predicate | hasAlcoholLicense |
P162592
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Table Table, hasAlcoholLicense, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlcoholLicense Context triple: [Table Table, hasAlcoholLicense, yes]
-
A.
servesAlcohol
Indicates that an establishment or provider offers and supplies alcoholic beverages to customers or participants.
-
B.
drinkingPermitted
Indicates that consuming alcoholic beverages is allowed in a given context, location, or situation.
-
C.
hasBreweryOrFacility
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
D.
hasAlcoholContent
Indicates that an entity contains alcohol and specifies the amount or concentration of that alcohol.
-
E.
hasAlcoholicVariant
Indicates that an entity has a related version or counterpart that contains alcohol.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 21, 2026, 5:01 p.m.