Triple
T22968777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigillaria |
E571121
|
entity |
| Predicate | primarySupportTissue |
P14750
|
FINISHED |
| Object | cortex and periderm |
—
|
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: cortex and periderm | Statement: [Sigillaria, primarySupportTissue, cortex and periderm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySupportTissue Context triple: [Sigillaria, primarySupportTissue, cortex and periderm]
-
A.
primarySites
Indicates the main or originating locations associated with an entity, often distinguishing them from secondary or related sites.
-
B.
hasTissue
chosen
Indicates that one entity possesses, contains, or is associated with a specific tissue of another entity.
-
C.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
-
D.
primaryBody
Indicates that one entity serves as the main or principal body associated with another entity.
-
E.
conductingTissueType
Indicates the specific kind of biological tissue responsible for conducting electrical impulses or signals within an organism.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18231459881909dd25a0630c494d8 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.