Triple
T38559540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacteriales |
E928039
|
entity |
| Predicate | containsOrganismsWithHabitat |
P203102
|
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: [Mycobacteriales, containsOrganismsWithHabitat, soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsOrganismsWithHabitat Context triple: [Mycobacteriales, containsOrganismsWithHabitat, soil]
-
A.
containsSpeciesWithHabitat
Indicates that an entity includes one or more species that are associated with a particular habitat.
-
B.
containsOrganismsWith
chosen
Indicates that one entity includes or holds within it one or more organisms associated with another entity.
-
C.
hasAssociatedHabitat
Indicates that an entity is linked to a particular habitat in which it typically lives, occurs, or is found.
-
D.
includesOrganisms
Indicates that one entity contains, encompasses, or has as members one or more specified organisms.
-
E.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.