Triple
T10313411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabuki Cafe |
E241952
|
entity |
| Predicate | walkUpOnly |
P88386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kabuki Cafe, walkUpOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkUpOnly Context triple: [Kabuki Cafe, walkUpOnly, true]
-
A.
walkUpAvailable
Indicates that an option, service, or location can be accessed directly on foot without prior appointment or vehicle use.
-
B.
walkOffType
Indicates the specific way in which a walk-off (a game-ending play or event) occurs or is classified.
-
C.
walkUpOrdering
chosen
Indicates a relationship where an order is placed in person at a counter or window, typically by walking up rather than using drive-through, delivery, or online channels.
-
D.
walkInPolicy
Indicates that an entity allows or operates under a policy where individuals can arrive and be served without a prior appointment.
-
E.
walkOff
Indicates that an entity departs or leaves a place or situation by walking away from it.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:48 a.m.