Triple
T16211842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemertea |
E393483
|
entity |
| Predicate | canInhabit |
P23320
|
FINISHED |
| Object | brackish waters |
—
|
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: brackish waters | Statement: [Nemertea, canInhabit, brackish waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInhabit Context triple: [Nemertea, canInhabit, brackish waters]
-
A.
canResideIn
chosen
Indicates that an entity is capable of living, staying, or being located within a specified place or environment.
-
B.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
C.
usesHabitatFeature
Indicates that an organism makes use of a particular habitat feature (such as a structure, resource, or microhabitat) as part of its behavior or life history.
-
D.
hasTerrestrialHabitat
Indicates that an entity lives primarily on land or in a ground-based environment rather than in aquatic or aerial habitats.
-
E.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.