Triple
T28855730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrostachyaceae |
E728728
|
entity |
| Predicate | isFloweringPlantFamily |
P109756
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hydrostachyaceae, isFloweringPlantFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFloweringPlantFamily Context triple: [Hydrostachyaceae, isFloweringPlantFamily, true]
-
A.
isFloweringPlantOrder
Indicates that one entity is a taxonomic order classified among the flowering plants (angiosperms).
-
B.
floweringPlantFamily
chosen
Indicates that a flowering plant belongs to, or is classified within, a particular botanical family.
-
C.
isVascularPlantFamily
Indicates that a given taxonomic family belongs to the group of vascular plants (plants with specialized conducting tissues such as xylem and phloem).
-
D.
floweringPlantGroup
Indicates that the subject belongs to, or is classified within, a particular group or category of flowering plants.
-
E.
isFlowering
Indicates that an entity is currently undergoing or capable of undergoing the process of producing flowers.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659dc20e881908c5f4f1706b9a53a |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:45 a.m.