Triple
T10500442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tea Caddy |
E247656
|
entity |
| Predicate | servesGuests |
P6789
|
FINISHED |
| Object | Epcot visitors |
—
|
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: Epcot visitors | Statement: [The Tea Caddy, servesGuests, Epcot visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesGuests Context triple: [The Tea Caddy, servesGuests, Epcot visitors]
-
A.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
-
B.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
-
C.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
D.
servesVenue
chosen
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098ef57c8190a9803c2c1736d299 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.