Triple
T29673700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Casual Table-Service Dining category |
E750742
|
entity |
| Predicate | serviceExpectation |
P21995
|
FINISHED |
| Object | gratuity-based table service |
—
|
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: gratuity-based table service | Statement: [Disney Casual Table-Service Dining category, serviceExpectation, gratuity-based table service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceExpectation Context triple: [Disney Casual Table-Service Dining category, serviceExpectation, gratuity-based table service]
-
A.
serviceBefore
Indicates that one service occurs, is provided, or is scheduled earlier in time than another service.
-
B.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
serviceUserRequirement
chosen
Indicates that a user has a specific requirement or need that a service is expected to fulfill.
-
E.
serviceUnder
Indicates that one entity operates, functions, or is provided under the authority, management, or jurisdiction of 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 7:06 p.m.