Triple
T10500404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire County Fish Shop |
E247655
|
entity |
| Predicate | targetGuests |
P34539
|
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: [Yorkshire County Fish Shop, targetGuests, EPCOT visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetGuests Context triple: [Yorkshire County Fish Shop, targetGuests, EPCOT visitors]
-
A.
relationshipWithGuests
Indicates the nature or status of the connection or interaction that someone has with their guests.
-
B.
supportsGuest
Indicates that one entity provides assistance, resources, or accommodation to another entity in the role of a guest.
-
C.
guestCountApproximate
Indicates that the number of guests involved is represented as an estimated or approximate count rather than an exact figure.
-
D.
returnsAsGuestIn
Indicates that an entity comes back to participate or appear again in a context, but specifically in the role or capacity of a guest rather than a regular or primary member.
-
E.
primaryVisitors
chosen
Indicates that certain entities are the main or most important visitors associated with another entity or context.
- 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.