Triple
T13657948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomme de Savoie |
E326909
|
entity |
| Predicate | typicalProductionMethod |
P35314
|
FINISHED |
| Object | pressed cheese |
—
|
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: pressed cheese | Statement: [Tomme de Savoie, typicalProductionMethod, pressed cheese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProductionMethod Context triple: [Tomme de Savoie, typicalProductionMethod, pressed cheese]
-
A.
hasProductionMethod
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
B.
traditionalProductionMethod
Indicates that something is created or carried out using long-established, customary techniques rather than modern or industrial methods.
-
C.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
D.
typicalPreparation
chosen
Indicates the usual or standard way in which something is prepared or made.
-
E.
partOfProduction
Indicates that one entity functions as a component, segment, or phase within the overall process or structure of another production.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61f0d808190b1cd2a6ba0d930eb |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.