Triple
T10488004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Dining Room (Royal Yacht Britannia) |
E247339
|
entity |
| Predicate | tableware |
P94570
|
FINISHED |
| Object | Royal Yacht Britannia crested china |
—
|
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: Royal Yacht Britannia crested china | Statement: [State Dining Room (Royal Yacht Britannia), tableware, Royal Yacht Britannia crested china]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tableware Context triple: [State Dining Room (Royal Yacht Britannia), tableware, Royal Yacht Britannia crested china]
-
A.
servingVessel
Indicates that one entity functions as the container or vessel used to serve another entity (such as food or drink).
-
B.
dishShape
Indicates that one entity has the physical form or contour characterized by the other entity as its shape.
-
C.
dishType
Indicates the classification of a dish according to its culinary category or role (e.g., appetizer, main course, dessert).
-
D.
eatenWithUtensil
Indicates that something was eaten using a specific utensil as the means of consumption.
-
E.
plate3
Indicates that one entity is a third plate or dish associated with, supporting, or serving another entity in a given context.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5096b609c81909e23fd8fb6426f4a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d5092af880819082b42c0a68e45c5f |
completed | April 7, 2026, 1:39 p.m. |
Created at: April 6, 2026, 12:23 p.m.