Triple
T16032324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudofumaria |
E388875
|
entity |
| Predicate | belongsToOrderCommonName |
P60300
|
FINISHED |
| Object | poppy order |
—
|
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 | Statement: [Pseudofumaria, belongsToOrderCommonName, poppy order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOrderCommonName Context triple: [Pseudofumaria, belongsToOrderCommonName, poppy order]
-
A.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
C.
hasNameOrder
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
D.
belongsToOrderClassSystem
chosen
Indicates that something is classified within, or is a member of, a particular order in a hierarchical class system.
-
E.
commonNameDerivedFrom
Indicates that the commonly used name of one entity originates from, or is derived based on, another entity.
- 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_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. |
Created at: April 10, 2026, 4:56 a.m.