Triple
T36225712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descriptiones animalium |
E1047977
|
entity |
| Predicate | usesTaxonomyOf |
P122543
|
FINISHED |
| Object | Carl Linnaeus |
—
|
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: Carl Linnaeus | Statement: [Descriptiones animalium, usesTaxonomyOf, Carl Linnaeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTaxonomyOf Context triple: [Descriptiones animalium, usesTaxonomyOf, Carl Linnaeus]
-
A.
hasTaxonomyTag
Indicates that an entity is associated with a specific taxonomy tag used for classification or categorization.
-
B.
useOfTerm
Indicates that one entity employs or applies a specific term or expression in reference to another entity or context.
-
C.
authorityInTaxonomy
chosen
Indicates that an entity serves as the defining or governing source (authority) for the classification or naming of another entity within a taxonomy.
-
D.
usedTaxonomicConcept
Indicates that one entity applies or refers to a particular taxonomic concept when identifying, classifying, or interpreting another entity.
-
E.
includesTaxaWith
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.