Triple
T31552697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pangio |
E805046
|
entity |
| Predicate | typicalMicrohabitat |
P25732
|
FINISHED |
| Object | slow-moving streams |
—
|
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: slow-moving streams | Statement: [Pangio, typicalMicrohabitat, slow-moving streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMicrohabitat Context triple: [Pangio, typicalMicrohabitat, slow-moving streams]
-
A.
microhabitat
chosen
Indicates a specific, localized habitat or environmental niche within a larger habitat where an organism lives or an interaction occurs.
-
B.
typicalHabitatInHost
Indicates that an organism’s usual or characteristic habitat occurs within a particular host organism.
-
C.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
D.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
E.
typicalGeologicEnvironment
Indicates the characteristic geologic setting or conditions in which something (such as a rock, mineral, or process) most commonly occurs or forms.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:11 p.m.