Triple
T21660327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biomphalaria pfeifferi |
E534576
|
entity |
| Predicate | preferredMicrohabitat |
P25732
|
FINISHED |
| Object | shallow water margins |
—
|
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: shallow water margins | Statement: [Biomphalaria pfeifferi, preferredMicrohabitat, shallow water margins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredMicrohabitat Context triple: [Biomphalaria pfeifferi, preferredMicrohabitat, shallow water margins]
-
A.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
B.
microhabitat
chosen
Indicates a specific, localized habitat or environmental niche within a larger habitat where an organism lives or an interaction occurs.
-
C.
preferredClimate
Indicates the type of climate that an entity favors or is most suited to.
-
D.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
E.
typicalHabitatInHost
Indicates that an organism’s usual or characteristic habitat occurs within a particular host organism.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c07bcb88190a9864672c20325ff |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.