Triple
T31672382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gruyères |
E808304
|
entity |
| Predicate | cheeseAOCRegionFor |
P94140
|
FINISHED |
| Object | Gruyère AOP |
—
|
NE NERFINISHED |
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: Gruyère AOP | Statement: [Gruyères, cheeseAOCRegionFor, Gruyère AOP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheeseAOCRegionFor Context triple: [Gruyères, cheeseAOCRegionFor, Gruyère AOP]
-
A.
cheeseProtectedDesignation
chosen
Indicates that a cheese has an officially recognized protected designation (such as PDO/PGI), linking it to specific geographic origin and production standards.
-
B.
cheeseSpeciality
Indicates that one entity is known for or specializes in producing or offering a particular type of cheese.
-
C.
cheeseType
Indicates that one entity is a specific type or variety of cheese in relation to another entity.
-
D.
cheeseMadeFrom
Indicates that one entity is produced or derived as cheese from another entity (typically a source ingredient such as milk).
-
E.
traditionalCheese
Indicates that something is recognized as a cheese made according to established, customary, or historically rooted methods or styles.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:01 p.m.