Triple
T25336837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roquefort-sur-Soulzon caves |
E635299
|
entity |
| Predicate | notableProducerUsingCaves |
P17041
|
FINISHED |
| Object | Société des Caves de Roquefort |
—
|
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: Société des Caves de Roquefort | Statement: [Roquefort-sur-Soulzon caves, notableProducerUsingCaves, Société des Caves de Roquefort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProducerUsingCaves Context triple: [Roquefort-sur-Soulzon caves, notableProducerUsingCaves, Société des Caves de Roquefort]
-
A.
notableCave
Indicates that the subject is a cave that is notable or significant in some recognized way.
-
B.
notableProducer
chosen
Indicates that an entity is a significant or well-known producer associated with another entity, such as a work, product, or project.
-
C.
cavesUsedFor
Indicates that certain caves are utilized for a particular purpose, activity, or function by an entity.
-
D.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
E.
notableQuarry
Indicates that an entity is a quarry that is particularly significant, well-known, or noteworthy in some context.
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 21, 2026, 1:32 p.m.