Triple
T9894211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tekone-zushi |
E181527
|
entity |
| Predicate | usesPreparationMethod |
P14777
|
FINISHED |
| Object | marinating |
—
|
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: marinating | Statement: [Tekone-zushi, usesPreparationMethod, marinating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPreparationMethod Context triple: [Tekone-zushi, usesPreparationMethod, marinating]
-
A.
usesCookingMethod
chosen
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
B.
traditionalPreparation
Indicates that something is prepared or made using customary, long-established methods or techniques associated with a particular culture or practice.
-
C.
typicalPreparation
Indicates the usual or standard way in which something is prepared or made.
-
D.
preparationPreference
Indicates how an entity prefers something to be prepared, processed, or made ready (e.g., style, method, or conditions of preparation).
-
E.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb48271d48190b718c7f6b2fe315b |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.