Triple
T5526321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont d'Or cheese |
E144929
|
entity |
| Predicate | hasRindMicroflora |
P65252
|
FINISHED |
| Object | bacteria from washing brine |
—
|
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: bacteria from washing brine | Statement: [Mont d'Or cheese, hasRindMicroflora, bacteria from washing brine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRindMicroflora Context triple: [Mont d'Or cheese, hasRindMicroflora, bacteria from washing brine]
-
A.
hasRind
Indicates that an entity possesses a tough, outer protective layer or skin (a rind).
-
B.
bacteriumIdentifiedIn
Indicates that a specific bacterium has been detected, recognized, or confirmed as present in a particular sample, environment, or host.
-
C.
hasRhizoids
Indicates that an organism possesses rhizoids, i.e., root-like structures used for anchorage or absorption.
-
D.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
-
E.
culturedOn
Indicates that an organism or biological sample is grown or maintained on a specified medium or substrate.
- F. None of above. chosen
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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f89112c8190b276317fcc2acce0 |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:34 p.m.