Triple
T16032402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceratocapnos |
E388877
|
entity |
| Predicate | orderCommonName |
P121674
|
FINISHED |
| Object | poppy order Ranunculales |
—
|
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: poppy order Ranunculales | Statement: [Ceratocapnos, orderCommonName, poppy order Ranunculales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderCommonName Context triple: [Ceratocapnos, orderCommonName, poppy order Ranunculales]
-
A.
orderName
Indicates the designated name or label assigned to a specific order in a transaction or ordering process.
-
B.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
C.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or entity.
-
D.
innerOrderName
Indicates the name or label assigned to an internal or subordinate order within a larger ordering or process.
-
E.
orderClass
Indicates that one entity is classified into a particular order or category within a hierarchical or taxonomic 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:56 a.m.