Triple
T11466653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowenstein–Jensen medium |
E271796
|
entity |
| Predicate | usedWithSpecimenType |
P4791
|
FINISHED |
| Object | sputum |
—
|
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: sputum | Statement: [Lowenstein–Jensen medium, usedWithSpecimenType, sputum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithSpecimenType Context triple: [Lowenstein–Jensen medium, usedWithSpecimenType, sputum]
-
A.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
containsSpeciesUsedAs
Indicates that something includes, as part of its composition or content, a particular species that is used for a specified purpose.
-
C.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
D.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
E.
usedBySpecies
Indicates that something (such as an object, resource, or method) is utilized or employed by a particular species.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.