Triple
T9287095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giraffa |
E223419
|
entity |
| Predicate | binomialNomenclatureLanguage |
P87409
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Giraffa, binomialNomenclatureLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binomialNomenclatureLanguage Context triple: [Giraffa, binomialNomenclatureLanguage, Latin]
-
A.
binomialName
Indicates the formal scientific name assigned to a species, typically composed of its genus and specific epithet.
-
B.
originalBinomialName
Indicates that one entity is the original scientific (binomial) name that was first formally assigned to the other entity (typically a species or taxon).
-
C.
scientificName
Indicates the formal taxonomic name assigned to an organism according to scientific naming conventions.
-
D.
nomenclaturalCode
Indicates the formal set of naming rules or code under which an entity’s scientific or taxonomic name is established or governed.
-
E.
nomenclaturalStatus
Indicates the formal taxonomic or naming status assigned to a scientific name (e.g., valid, invalid, synonym, provisional) within a nomenclatural system.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0861425c81909e3ab11e19cc2f65 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.