Triple
T37510910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleuropterus |
E932212
|
entity |
| Predicate | nomenclaturalTypeGroup |
P89905
|
FINISHED |
| Object | genus-level name |
—
|
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: genus-level name | Statement: [Pleuropterus, nomenclaturalTypeGroup, genus-level name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nomenclaturalTypeGroup Context triple: [Pleuropterus, nomenclaturalTypeGroup, genus-level name]
-
A.
nomenclaturalTypeGenus
chosen
Indicates that one genus serves as the nomenclatural (name-bearing) type for a higher-ranked taxon, anchoring the application and definition of that taxon's name.
-
B.
nomenclaturalCode
Indicates the formal set of naming rules or code under which an entity’s scientific or taxonomic name is established or governed.
-
C.
nomenclaturalStatus
Indicates the formal taxonomic or naming status assigned to a scientific name (e.g., valid, invalid, synonym, provisional) within a nomenclatural system.
-
D.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
E.
taxonType
Indicates the biological or taxonomic rank/category that characterizes a given taxon.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.