Triple
T26372633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey Royal potatoes |
E660811
|
entity |
| Predicate | commonlyServed |
P103073
|
FINISHED |
| Object | with butter |
—
|
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: with butter | Statement: [Jersey Royal potatoes, commonlyServed, with butter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyServed Context triple: [Jersey Royal potatoes, commonlyServed, with butter]
-
A.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
B.
isTypicallyServedIn
Indicates that something (such as a food or drink) is most commonly or customarily presented or contained within a particular type of vessel or container.
-
C.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
-
D.
traditionallyServed
chosen
Indicates that one entity is customarily or conventionally presented, offered, or consumed together with another entity.
-
E.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 26, 2026, 10:59 p.m.