Triple
T37492791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium fortuitum |
E931741
|
entity |
| Predicate | environmentalHabitat |
P178926
|
FINISHED |
| Object | soil |
—
|
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: soil | Statement: [Mycobacterium fortuitum, environmentalHabitat, soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentalHabitat Context triple: [Mycobacterium fortuitum, environmentalHabitat, soil]
-
A.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
livingEnvironment
chosen
Indicates the type of surroundings or conditions in which an entity lives or exists.
-
C.
environmentalSuitability
Indicates that certain environmental conditions are appropriate or favorable for a particular entity, process, or activity.
-
D.
environmentalFeatureOf
Indicates a relationship where one entity is a natural or environmental characteristic, component, or attribute of another entity or place.
-
E.
environmentalDependence
Indicates that one entity’s state, behavior, or existence is contingent on or significantly influenced by environmental conditions or factors.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.