Triple
T2613098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phytolaccaceae |
E58821
|
entity |
| Predicate | ovaryPosition |
P5982
|
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: [Phytolaccaceae, ovaryPosition, superior ovary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ovaryPosition Context triple: [Phytolaccaceae, ovaryPosition, superior ovary]
-
A.
reproductiveSystem
Indicates a relationship where one entity is the reproductive system of another, responsible for producing offspring or reproductive cells.
-
B.
bodySideOrientation
Indicates the spatial relationship of an entity with respect to the left, right, or bilateral side of a body.
-
C.
fertilizationType
Indicates the method or process by which fertilization occurs or is achieved between reproductive cells.
-
D.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
E.
reproductiveFeature
chosen
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.