Triple
T30994694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neoceti |
E789762
|
entity |
| Predicate | hasRepresentativeTaxon |
P51064
|
FINISHED |
| Object | blue whale |
—
|
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: blue whale | Statement: [Neoceti, hasRepresentativeTaxon, blue whale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentativeTaxon Context triple: [Neoceti, hasRepresentativeTaxon, blue whale]
-
A.
hasRelatedTaxon
chosen
Indicates a taxonomic relationship between two taxa that are connected in some biologically or taxonomically relevant way, without specifying the exact nature of that relationship.
-
B.
isTaxon
Indicates that one entity is a biological taxonomic unit (such as a species, genus, or family) associated with or classifying another entity.
-
C.
hasEponymousTaxon
Indicates that an entity has a taxonomic group (such as a species or genus) that is named after it.
-
D.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
E.
recognizedAsDistinctTaxonBy
Indicates that one entity is formally acknowledged as a separate and distinct taxonomic unit by a specified authority or source.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
Created at: April 29, 2026, 8:56 p.m.