Triple
T12510549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dipsacales |
E299064
|
entity |
| Predicate | orderNameEtymology |
P64332
|
FINISHED |
| Object | derived from genus Dipsacus |
—
|
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 genus Dipsacus | Statement: [Dipsacales, orderNameEtymology, derived from genus Dipsacus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderNameEtymology Context triple: [Dipsacales, orderNameEtymology, derived from genus Dipsacus]
-
A.
nameEtymologyFor
chosen
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
B.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
etymologyReason
Indicates the reason, source, or origin explaining how or why a term acquired its particular etymology.
-
D.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
E.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.