Triple
T16812637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blacktip Reef |
E408651
|
entity |
| Predicate | hasPrimarySpeciesCommonName |
P121406
|
FINISHED |
| Object | blacktip reef shark |
—
|
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: blacktip reef shark | Statement: [Blacktip Reef, hasPrimarySpeciesCommonName, blacktip reef shark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySpeciesCommonName Context triple: [Blacktip Reef, hasPrimarySpeciesCommonName, blacktip reef shark]
-
A.
includesSpeciesCommonName
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
B.
describedTaxonCommonName
chosen
Indicates that a taxon is being described or referenced using its common (vernacular) name rather than its scientific name.
-
C.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
D.
hasCommonSpecies
Indicates that two entities share at least one species in common.
-
E.
subspeciesCommonName
Indicates the common (non-scientific) name used to refer to a particular subspecies.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2df5c888190a462614e1432c357 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.