Triple
T13428973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crottin de Chavignol |
E313555
|
entity |
| Predicate | surfaceMicroflora |
P65252
|
FINISHED |
| Object | natural molds on rind |
—
|
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: natural molds on rind | Statement: [Crottin de Chavignol, surfaceMicroflora, natural molds on rind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceMicroflora Context triple: [Crottin de Chavignol, surfaceMicroflora, natural molds on rind]
-
A.
hasRindMicroflora
chosen
Indicates that an entity possesses or is associated with microbial communities located on its rind or outer surface.
-
B.
surfaceExpressionOf
Indicates that one entity is a specific surface-level manifestation or observable form of another underlying entity or concept.
-
C.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
D.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
E.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed304ac8190a8021f749de8164c |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.