Triple
T32049122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echinopsis atacamensis |
E818436
|
entity |
| Predicate | photosynthesisSite |
P26252
|
FINISHED |
| Object | green stem tissue |
—
|
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: green stem tissue | Statement: [Echinopsis atacamensis, photosynthesisSite, green stem tissue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photosynthesisSite Context triple: [Echinopsis atacamensis, photosynthesisSite, green stem tissue]
-
A.
photosynthesisType
Indicates the specific kind or category of photosynthesis an organism performs (e.g., C3, C4, CAM).
-
B.
photosyntheticOrgan
Indicates that an entity is an organ specialized for performing photosynthesis in an organism.
-
C.
photosynthesisRate
Indicates the rate at which photosynthesis occurs in an organism or system, typically measuring how quickly light energy is converted into chemical energy.
-
D.
photosyntheticTissue
chosen
Indicates that an entity has tissue capable of performing photosynthesis, converting light energy into chemical energy.
-
E.
photosyntheticOrganism
Indicates that an organism performs photosynthesis, converting light energy into chemical energy to sustain itself.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4c5e18c8190b03bbde2092b701a |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:20 a.m.