Triple
T7464488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Frisian tea |
E176338
|
entity |
| Predicate | isTraditionallyServedIn |
P13132
|
FINISHED |
| Object | porcelain cup |
—
|
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: porcelain cup | Statement: [East Frisian tea, isTraditionallyServedIn, porcelain cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionallyServedIn Context triple: [East Frisian tea, isTraditionallyServedIn, porcelain cup]
-
A.
servesTradition
Indicates that one entity upholds, maintains, or performs a tradition for the benefit or continuation of that tradition.
-
B.
traditionallyFoundIn
chosen
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
C.
isUsuallyCookedIn
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
D.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
E.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f28f34819080713a8abcc22034 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:40 p.m.