Triple
T37412610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlebrook 7H11 agar |
E929612
|
entity |
| Predicate | mayBeSupplementedWith |
P17547
|
FINISHED |
| Object | antibiotics |
—
|
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: antibiotics | Statement: [Middlebrook 7H11 agar, mayBeSupplementedWith, antibiotics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeSupplementedWith Context triple: [Middlebrook 7H11 agar, mayBeSupplementedWith, antibiotics]
-
A.
hasSupplement
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
B.
canBeAugmentedWith
chosen
Indicates that one entity is capable of being enhanced, expanded, or supplemented by another entity.
-
C.
mayAlsoBeProvidedAs
Indicates that something can optionally be supplied or made available in an alternative form or manner in addition to its primary provision.
-
D.
mayAlsoInclude
Indicates that something can optionally contain or encompass additional elements beyond those primarily specified.
-
E.
mayBeExtended
Indicates that something has the potential or option to be lengthened in duration, scope, or size beyond its current or initial limits.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:16 p.m.