Triple
T9572277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heterenchelyidae |
E230951
|
entity |
| Predicate | hasEcologicalNiche |
P25102
|
FINISHED |
| Object | infaunal burrower |
—
|
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: infaunal burrower | Statement: [Heterenchelyidae, hasEcologicalNiche, infaunal burrower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcologicalNiche Context triple: [Heterenchelyidae, hasEcologicalNiche, infaunal burrower]
-
A.
hasEcology
chosen
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
B.
containsEcologicalTypes
Indicates that one entity includes or encompasses specific ecological types or categories within it.
-
C.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
D.
containsSpeciesWithHabitat
Indicates that an entity includes one or more species that are associated with a particular habitat.
-
E.
hasEcosystemService
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998bf20881909fad48ecb16dfa31 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.