Triple
T37468121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhinocs |
E931081
|
entity |
| Predicate | speciesNameEtymology |
P87618
|
FINISHED |
| Object | Derived from the word rhinoceros |
—
|
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: Derived from the word rhinoceros | Statement: [Rhinocs, speciesNameEtymology, Derived from the word rhinoceros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesNameEtymology Context triple: [Rhinocs, speciesNameEtymology, Derived from the word rhinoceros]
-
A.
speciesNameMeaning
chosen
Indicates the meaning or etymological sense of a species’ scientific name.
-
B.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
C.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
D.
eponymLatinName
Indicates that one entity is the Latin name that is an eponym derived from or named after another entity.
-
E.
genusNameMeaning
Indicates the meaning or etymological sense of the name of a genus.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:17 p.m.