Triple
T38620807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atraphaxis pyrifolia |
E936858
|
entity |
| Predicate | hasFloweringPlantGroup |
P127199
|
FINISHED |
| Object | dicotyledons |
—
|
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: dicotyledons | Statement: [Atraphaxis pyrifolia, hasFloweringPlantGroup, dicotyledons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloweringPlantGroup Context triple: [Atraphaxis pyrifolia, hasFloweringPlantGroup, dicotyledons]
-
A.
floweringPlantGroup
chosen
Indicates that the subject belongs to, or is classified within, a particular group or category of flowering plants.
-
B.
hasFloraGroup
Indicates that an entity is associated with, contains, or is characterized by a particular group or category of plant life.
-
C.
isFlowering
Indicates that an entity is currently undergoing or capable of undergoing the process of producing flowers.
-
D.
isFloweringPlantOrder
Indicates that one entity is a taxonomic order classified among the flowering plants (angiosperms).
-
E.
hasFloralFeature
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:32 p.m.