Triple
T15018815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maasdam cheese |
E378027
|
entity |
| Predicate | isCommercialStyleOf |
P92195
|
FINISHED |
| Object | Swiss-type 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: Swiss-type cheese | Statement: [Maasdam cheese, isCommercialStyleOf, Swiss-type cheese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialStyleOf Context triple: [Maasdam cheese, isCommercialStyleOf, Swiss-type cheese]
-
A.
usesProductionStyle
Indicates that one entity creates, presents, or operates another entity using a particular production style or method.
-
B.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
C.
hasCommercialVariant
chosen
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
D.
isCommercialCommunityFor
Indicates a relationship where one entity serves as the primary commercial hub or marketplace community for another entity (such as a product, brand, or user group).
-
E.
isCommercialPort
Indicates that a location functions as a port used for commercial or trade-related maritime activities.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded76445988190984b57de66e00c4a |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:56 a.m.