Triple
T25336826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roquefort-sur-Soulzon caves |
E635299
|
entity |
| Predicate | supportsMold |
P63191
|
FINISHED |
| Object | Penicillium roqueforti |
—
|
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: Penicillium roqueforti | Statement: [Roquefort-sur-Soulzon caves, supportsMold, Penicillium roqueforti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMold Context triple: [Roquefort-sur-Soulzon caves, supportsMold, Penicillium roqueforti]
-
A.
supportsMaterial
chosen
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
B.
supportedModel
Indicates that one entity provides compatibility with, or operational backing for, a particular model.
-
C.
usesSupportMaterial
Indicates that an entity relies on or incorporates additional supporting materials or resources to carry out an action or fulfill a function.
-
D.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
E.
supportsModelingOf
Indicates that one entity provides the capability or functionality needed to represent, simulate, or model another entity or process.
- 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_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 1:32 p.m.