Triple
T27720472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | curanto |
E698938
|
entity |
| Predicate | traditionallyPreparedBy |
P18062
|
FINISHED |
| Object | community members |
—
|
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: community members | Statement: [curanto, traditionallyPreparedBy, community members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPreparedBy Context triple: [curanto, traditionallyPreparedBy, community members]
-
A.
traditionallyServed
Indicates that one entity is customarily or conventionally presented, offered, or consumed together with another entity.
-
B.
traditionalPreparation
chosen
Indicates that something is prepared or made using customary, long-established methods or techniques associated with a particular culture or practice.
-
C.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
D.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
E.
typeOfPreparation
Indicates the method or process by which something is prepared or made ready for use, consumption, or further action.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 3:06 p.m.