Triple
T25336845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roquefort-sur-Soulzon caves |
E635299
|
entity |
| Predicate | cheeseTypeMatured |
P60147
|
FINISHED |
| Object | sheep’s milk blue 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: sheep’s milk blue cheese | Statement: [Roquefort-sur-Soulzon caves, cheeseTypeMatured, sheep’s milk blue cheese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheeseTypeMatured Context triple: [Roquefort-sur-Soulzon caves, cheeseTypeMatured, sheep’s milk blue cheese]
-
A.
cheeseRipeningStyle
Indicates the method or process by which a cheese is matured or aged to develop its flavor and texture.
-
B.
cheeseType
chosen
Indicates that one entity is a specific type or variety of cheese in relation to another entity.
-
C.
cheeseMadeFrom
Indicates that one entity is produced or derived as cheese from another entity (typically a source ingredient such as milk).
-
D.
cheeseSpeciality
Indicates that one entity is known for or specializes in producing or offering a particular type of cheese.
-
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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b39adc8190b0fc4925ce0769ed |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.