Triple
T26059046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yemas de Santa Teresa |
E657204
|
entity |
| Predicate | isTypicallyHomemade |
P76282
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [yemas de Santa Teresa, isTypicallyHomemade, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyHomemade Context triple: [yemas de Santa Teresa, isTypicallyHomemade, true]
-
A.
isOftenHomemade
chosen
Indicates that something is frequently made at home rather than being purchased or produced commercially.
-
B.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
C.
isHouseholdStaple
Indicates that something is commonly and consistently kept on hand in a household as a basic, regularly used item.
-
D.
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).
-
E.
isSavory
Indicates that something has a salty, spicy, or umami-dominant taste rather than a sweet one.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 7:14 p.m.