Triple
T28830869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canis lycaon |
E728043
|
entity |
| Predicate | recognizedAsDistinctTaxonBy |
P179032
|
FINISHED |
| Object | some taxonomists |
—
|
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: some taxonomists | Statement: [Canis lycaon, recognizedAsDistinctTaxonBy, some taxonomists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsDistinctTaxonBy Context triple: [Canis lycaon, recognizedAsDistinctTaxonBy, some taxonomists]
-
A.
recognizedAsDistinctSpeciesSince
Indicates that an organism or taxon has been formally acknowledged and classified as a separate species starting from a specified point in time.
-
B.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
C.
isTaxon
Indicates that one entity is a biological taxonomic unit (such as a species, genus, or family) associated with or classifying another entity.
-
D.
taxonomicSynonymOf
Indicates that two taxonomic names refer to the same biological taxon, treating one as an alternative or equivalent scientific name for the other.
-
E.
honouredInTaxon
Indicates that an organism or taxonomic group is named in honor of a particular person, entity, or concept.
- F. None of above. chosen
Provenance (4 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 28, 2026, 6:37 a.m.