Triple
T11977223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liliaceae |
E285068
|
entity |
| Predicate | gynoecium |
P1979
|
FINISHED |
| Object | superior ovary |
—
|
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: superior ovary | Statement: [Liliaceae, gynoecium, superior ovary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gynoecium Context triple: [Liliaceae, gynoecium, superior ovary]
-
A.
reproductiveStructure
chosen
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.
-
B.
ovulePosition
Indicates the spatial placement or arrangement of ovules within or on the ovary or related reproductive structure.
-
C.
stamenCount
Indicates the number of stamens present in a flower or floral structure.
-
D.
gymnosperm
Indicates that an entity is a gymnosperm, i.e., a seed-producing plant whose seeds are not enclosed within an ovary (not in a fruit).
-
E.
typicalStamens
Indicates that the stamens of an organism or structure exhibit the standard or characteristic form, number, or arrangement expected for that taxon or group.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.