Triple
T22516313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trichocomaceae |
E556656
|
entity |
| Predicate | containsSpeciesUsedFor |
P40129
|
FINISHED |
| Object | antibiotic production |
—
|
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: antibiotic production | Statement: [Trichocomaceae, containsSpeciesUsedFor, antibiotic production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpeciesUsedFor Context triple: [Trichocomaceae, containsSpeciesUsedFor, antibiotic production]
-
A.
containsSpeciesUsedAs
chosen
Indicates that something includes, as part of its composition or content, a particular species that is used for a specified purpose.
-
B.
usedBySpecies
Indicates that something (such as an object, resource, or method) is utilized or employed by a particular species.
-
C.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
D.
containsSpeciesUsedForFood
Indicates that something includes one or more species that are used as a source of food.
-
E.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2cfc908190b3489228a1997f45 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.