Triple
T10213683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginkgoales |
E242390
|
entity |
| Predicate | ovulePosition |
P92755
|
FINISHED |
| Object | borne on stalks |
—
|
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: borne on stalks | Statement: [Ginkgoales, ovulePosition, borne on stalks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ovulePosition Context triple: [Ginkgoales, ovulePosition, borne on stalks]
-
A.
sporangiumPosition
Indicates the relative location or arrangement of a sporangium in or on the structure that bears it.
-
B.
reproductiveStructure
Indicates that one entity serves as a reproductive organ or structure of another, involved in producing or facilitating the formation of offspring or reproductive cells.
-
C.
fertilizationType
Indicates the method or process by which fertilization occurs or is achieved between reproductive cells.
-
D.
typicalOvaryPosition
Indicates the usual anatomical location or placement of an ovary relative to other structures or reference points.
-
E.
flowerPosition
Indicates the spatial location or arrangement of a flower relative to a reference object or coordinate system.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa24efc081909714d98943543283 |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11:03 a.m.