Triple
T33346233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aloe |
E853801
|
entity |
| Predicate | containsTissue |
P14750
|
FINISHED |
| Object | water-storing parenchyma |
—
|
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: water-storing parenchyma | Statement: [Aloe, containsTissue, water-storing parenchyma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTissue Context triple: [Aloe, containsTissue, water-storing parenchyma]
-
A.
hasTissue
chosen
Indicates that one entity possesses, contains, or is associated with a specific tissue of another entity.
-
B.
hasTrueTissues
Indicates that an organism possesses differentiated, organized tissues composed of multiple cell types performing specific functions.
-
C.
hasTissueLevelOrganization
Indicates that an entity possesses a structural organization composed of multiple tissues arranged into functional units.
-
D.
infectsTissue
Indicates that one entity (typically a pathogen or agent) invades and establishes itself within the tissue of another entity.
-
E.
hasOrganStructure
Indicates that one entity possesses, contains, or is characterized by a particular organ structure.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.