Triple
T28771138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uerige brewery |
E726414
|
entity |
| Predicate | hasWaiterService |
P175656
|
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: [Uerige brewery, hasWaiterService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaiterService Context triple: [Uerige brewery, hasWaiterService, yes]
-
A.
hasVirtualWaiter
Indicates that an entity is served or assisted by a digital or virtual waiter system rather than a human waiter.
-
B.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasWaitingList
Indicates that there exists a queue or list of entities waiting for access to, or participation in, the referenced resource, service, or opportunity.
-
E.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 6:15 a.m.