Triple
T1891780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew's Cup Lounge |
E41888
|
entity |
| Predicate | diningPlanEligible |
P33094
|
FINISHED |
| Object | no table-service dining plan credit |
—
|
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: no table-service dining plan credit | Statement: [Crew's Cup Lounge, diningPlanEligible, no table-service dining plan credit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diningPlanEligible Context triple: [Crew's Cup Lounge, diningPlanEligible, no table-service dining plan credit]
-
A.
isDiningDestination
Indicates that a place serves as a destination where people go specifically to eat meals or dine.
-
B.
hasHospitalityComponent
Indicates that something includes, involves, or is associated with a hospitality-related element, service, or function.
-
C.
hasSpecialMeal
Indicates that an entity provides, is assigned, or is associated with a designated special meal option.
-
D.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
E.
isFreeToAttend
Indicates that attending the event or activity does not require any payment or admission fee.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.