Triple
T2032278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesperopeuce |
E44543
|
entity |
| Predicate | hasReproductiveStructure |
P1979
|
FINISHED |
| Object | cones |
—
|
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: cones | Statement: [Hesperopeuce, hasReproductiveStructure, cones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReproductiveStructure Context triple: [Hesperopeuce, hasReproductiveStructure, cones]
-
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.
hasSporophyteMorphology
Indicates that an entity exhibits the structural form or physical characteristics typical of a sporophyte stage in its life cycle.
-
C.
hasSporophyteCharacteristic
Indicates that an entity possesses a characteristic or trait associated with the sporophyte stage of a life cycle.
-
D.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
-
E.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9313134819088133fb69b8f606f |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.