Triple
T17743369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balistoides |
E442920
|
entity |
| Predicate | typicalHabitatFeature |
P76824
|
FINISHED |
| Object | coral reefs |
—
|
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: coral reefs | Statement: [Balistoides, typicalHabitatFeature, coral reefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHabitatFeature Context triple: [Balistoides, typicalHabitatFeature, coral reefs]
-
A.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
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.
-
C.
preferredHabitat
chosen
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
D.
typicalHabitatInHost
Indicates that an organism’s usual or characteristic habitat occurs within a particular host organism.
-
E.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47acf44f8819089a18193e37d112c |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.