Triple
T18036795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laguiole cheese |
E431527
|
entity |
| Predicate | protectedDesignationStatus |
P40980
|
FINISHED |
| Object | PDO |
—
|
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: PDO | Statement: [Laguiole cheese, protectedDesignationStatus, PDO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedDesignationStatus Context triple: [Laguiole cheese, protectedDesignationStatus, PDO]
-
A.
protectedDesignation
chosen
Indicates that one entity has an officially recognized and legally protected designation or status in relation to another entity.
-
B.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
-
C.
religiousDesignation
Indicates the specific religious role, status, or affiliation assigned to an entity.
-
D.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
E.
communityDesignation
Indicates that an entity is formally assigned or recognized with a specific community-related status, label, or role.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3a80508190b667c3f6d14f5c84 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.