Triple
T8757080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engler system |
E208096
|
entity |
| Predicate | ordersAngiospermsBy |
P2395
|
FINISHED |
| Object | floral complexity |
—
|
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: floral complexity | Statement: [Engler system, ordersAngiospermsBy, floral complexity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersAngiospermsBy Context triple: [Engler system, ordersAngiospermsBy, floral complexity]
-
A.
angiospermGroup
Indicates a taxonomic grouping relationship in which one entity is classified as a group or category within the angiosperms (flowering plants).
-
B.
ordersBy
chosen
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
C.
orderOfPeristyle
Indicates the relative sequence or position of a peristyle within an ordered arrangement of multiple peristyles.
-
D.
orderName
Indicates the designated name or label assigned to a specific order in a transaction or ordering process.
-
E.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ddabdc88190ba50ef1833a815d0 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.