Triple
T33291689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPCOT quick-service restaurants |
E852335
|
entity |
| Predicate | typicalGuestNeed |
P206411
|
FINISHED |
| Object | quick meals between attractions |
—
|
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: quick meals between attractions | Statement: [EPCOT quick-service restaurants, typicalGuestNeed, quick meals between attractions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGuestNeed Context triple: [EPCOT quick-service restaurants, typicalGuestNeed, quick meals between attractions]
-
A.
typicalGuests
Indicates the usual or most common guests associated with a particular host, place, or event.
-
B.
typicalGuestConfederation
Indicates that one entity is typically a guest or participant within the confederation represented by the other entity.
-
C.
intendedGuest
Indicates that one entity is designated or planned to be a guest of another entity or event.
-
D.
relationshipWithGuests
Indicates the nature or status of the connection or interaction that someone has with their guests.
-
E.
guestOnBoard
Indicates that an entity is currently present as a guest aboard a vehicle, vessel, or similar conveyance.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:32 a.m.