Triple
T29298030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joinvilleaceae |
E742883
|
entity |
| Predicate | isMonocotFamily |
P166818
|
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: [Joinvilleaceae, isMonocotFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonocotFamily Context triple: [Joinvilleaceae, isMonocotFamily, true]
-
A.
isMonocot
Indicates that an organism belongs to the group of flowering plants characterized by having a single cotyledon (seed leaf) in the embryo.
-
B.
isDicotFamily
Indicates that a plant family belongs to the group of dicotyledonous (dicot) plants, characterized by having two seed leaves and related dicot traits.
-
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.
numberOfMonocotSubclasses
Indicates the relationship specifying how many subclasses are recognized within the group of monocotyledon plants.
-
E.
isGrassSubfamily
Indicates that one entity is a botanical subfamily within the grass family (Poaceae) to which the other entity belongs.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654594048190ad15dbcd2c16db2e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:08 p.m.