Triple
T34667785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephippidae |
E890299
|
entity |
| Predicate | hasJuvenileHabitat |
P58787
|
FINISHED |
| Object | coastal shallows |
—
|
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: coastal shallows | Statement: [Ephippidae, hasJuvenileHabitat, coastal shallows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJuvenileHabitat Context triple: [Ephippidae, hasJuvenileHabitat, coastal shallows]
-
A.
juvenileHabitat
chosen
Indicates the type of environment or location where an organism lives during its juvenile (immature) life stage.
-
B.
hasJuvenileForm
Indicates that an entity possesses or exhibits a distinct juvenile or immature form in its life cycle.
-
C.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
D.
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.
-
E.
hasAssociatedHabitat
Indicates that an entity is linked to a particular habitat in which it typically lives, occurs, or is found.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:05 a.m.