Triple
T33732447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vallée de Munster |
E864307
|
entity |
| Predicate | hasProductWithProtectedStatus |
P147426
|
FINISHED |
| Object | Munster cheese |
E107185
|
NE 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: Munster cheese | Statement: [Vallée de Munster, hasProductWithProtectedStatus, Munster cheese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductWithProtectedStatus Context triple: [Vallée de Munster, hasProductWithProtectedStatus, Munster cheese]
-
A.
hasProprietaryStatus
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
-
B.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
C.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
D.
hasProtectedFoodStatus
chosen
Indicates that a food item is officially recognized under a legal or regulatory scheme as having a protected designation, status, or origin.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- F. None of above.
Provenance (4 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c303af6081909c229b2c8e91c680 |
completed | May 11, 2026, 11:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c7f93c08190a76890d51f4e13bd |
completed | June 20, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_6a01c28ebf54819094318c447d8c7943 |
completed | May 11, 2026, 11:50 a.m. |
Created at: May 1, 2026, 1:44 a.m.