Triple
T30844823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linnaean taxonomy |
E785603
|
entity |
| Predicate | hasNamingRule |
P84208
|
FINISHED |
| Object | each species has a two-part Latin 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: each species has a two-part Latin name | Statement: [Linnaean taxonomy, hasNamingRule, each species has a two-part Latin name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamingRule Context triple: [Linnaean taxonomy, hasNamingRule, each species has a two-part Latin name]
-
A.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
B.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
C.
hasRulerNamingCustom
Indicates that a political entity follows a particular custom or convention for naming its ruler.
-
D.
hasAppellationRule
chosen
Indicates that there is a rule or standard governing how an entity may be named, labeled, or designated.
-
E.
isNamedAccordingTo
Indicates that one entity receives its name based on, or in accordance with, another entity, rule, or naming convention.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 8:46 p.m.