Triple
T13729234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vaquita marina |
E329747
|
entity |
| Predicate | hábitat |
P76824
|
FINISHED |
| Object | aguas costeras poco profundas |
—
|
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: aguas costeras poco profundas | Statement: [vaquita marina, hábitat, aguas costeras poco profundas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hábitat Context triple: [vaquita marina, hábitat, aguas costeras poco profundas]
-
A.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
preferredHabitat
chosen
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
C.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
D.
habitation
Indicates that one entity serves as the dwelling place, residence, or living environment for another entity.
-
E.
microhabitat
Indicates a specific, localized habitat or environmental niche within a larger habitat where an organism lives or an interaction occurs.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f746cc8190abde237bbb7e6c78 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.