Triple
T12727521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moqueca baiana |
E304143
|
entity |
| Predicate | usuallyPreparedIn |
P61222
|
FINISHED |
| Object | clay pot |
—
|
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: clay pot | Statement: [Moqueca baiana, usuallyPreparedIn, clay pot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usuallyPreparedIn Context triple: [Moqueca baiana, usuallyPreparedIn, clay pot]
-
A.
commonlyPreparedFor
Indicates that something is typically made, organized, or arranged in anticipation of a particular event, purpose, or recipient.
-
B.
typicalPreparation
Indicates the usual or standard way in which something is prepared or made.
-
C.
recommendedPreparation
Indicates that one entity is suggested or advised as a suitable preparation or prerequisite for engaging with another entity.
-
D.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
E.
isUsuallyCookedIn
chosen
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.