Triple
T3247863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kona Cafe |
E68105
|
entity |
| Predicate | acceptsWalkIns |
P46816
|
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: [Kona Cafe, acceptsWalkIns, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsWalkIns Context triple: [Kona Cafe, acceptsWalkIns, yes]
-
A.
openByAppointment
Indicates that access or availability is provided only at scheduled times arranged in advance, rather than during regular open hours.
-
B.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
C.
acceptsAdvanceDiningReservations
Indicates that an entity allows customers to make dining reservations in advance.
-
D.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
E.
canHoldAppointment
Indicates that an entity is eligible or permitted to occupy or serve in a particular appointment, position, or role.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf3e9ed0819096ac238098ac403c |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.