Triple
T8906237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotto Motto |
E212065
|
entity |
| Predicate | dineIn |
P55802
|
FINISHED |
| Object | limited or none |
—
|
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: limited or none | Statement: [Hotto Motto, dineIn, limited or none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dineIn Context triple: [Hotto Motto, dineIn, limited or none]
-
A.
diningStyle
Indicates the manner or format in which dining is conducted, such as casual, formal, buffet, or family-style.
-
B.
isDiningDestination
Indicates that a place serves as a destination where people go specifically to eat meals or dine.
-
C.
hasDiningFeature
chosen
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
D.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
-
E.
isEatenIn
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by another entity.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c51d6c819098dc33a480dfd462 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.