Triple
T33615180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandre Yersin |
E861096
|
entity |
| Predicate | hasNameInTaxon |
P189882
|
FINISHED |
| Object | Yersinia pestis |
—
|
NE NERFINISHED |
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: Yersinia pestis | Statement: [Alexandre Yersin, hasNameInTaxon, Yersinia pestis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInTaxon Context triple: [Alexandre Yersin, hasNameInTaxon, Yersinia pestis]
-
A.
hasEponymousTaxon
chosen
Indicates that an entity has a taxonomic group (such as a species or genus) that is named after it.
-
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.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
D.
hasRelatedTaxon
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.
-
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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:41 a.m.