Triple
T13395135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrtales |
E319683
|
entity |
| Predicate | hasOvaryPosition |
P65976
|
FINISHED |
| Object | inferior ovary (in many species) |
—
|
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: inferior ovary (in many species) | Statement: [Myrtales, hasOvaryPosition, inferior ovary (in many species)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOvaryPosition Context triple: [Myrtales, hasOvaryPosition, inferior ovary (in many species)]
-
A.
typicalOvaryPosition
chosen
Indicates the usual anatomical location or placement of an ovary relative to other structures or reference points.
-
B.
ovulePosition
Indicates the spatial placement or arrangement of ovules within or on the ovary or related reproductive structure.
-
C.
pelvicOrientation
Indicates the spatial alignment or positioning of the pelvis relative to a reference frame or other body parts.
-
D.
hasOVA
Indicates that one entity possesses, contains, or is associated with an Original Video Animation (OVA) related to it.
-
E.
hasAsexualMorph
Indicates that an entity possesses or is associated with an asexual morphological form in its life cycle.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d892d08190b1b192b93fe3d72d |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.