Triple
T34667786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephippidae |
E890299
|
entity |
| Predicate | hasAdultHabitat |
P153866
|
FINISHED |
| Object | reefs and hard-bottom areas |
—
|
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: reefs and hard-bottom areas | Statement: [Ephippidae, hasAdultHabitat, reefs and hard-bottom areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdultHabitat Context triple: [Ephippidae, hasAdultHabitat, reefs and hard-bottom areas]
-
A.
hasLargeSpecies
Indicates that an entity possesses or includes at least one species that is considered large in size.
-
B.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
C.
hasAdultArea
Indicates that something includes or is associated with an area designated specifically for adults.
-
D.
hasTerrestrialHabitat
Indicates that an entity lives primarily on land or in a ground-based environment rather than in aquatic or aerial habitats.
-
E.
hasAssociatedHabitat
chosen
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_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 1, 2026, 2:05 a.m.