Triple
T425175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryophyta |
E8191
|
entity |
| Predicate | vascularSystem |
P14746
|
FINISHED |
| Object | non-vascular |
—
|
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: non-vascular | Statement: [Bryophyta, vascularSystem, non-vascular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vascularSystem Context triple: [Bryophyta, vascularSystem, non-vascular]
-
A.
hasCirculatorySystem
Indicates that an entity possesses a circulatory system, i.e., an internal network for transporting blood or equivalent fluids throughout its body.
-
B.
circulation
Indicates the movement or flow of something (such as information, materials, or currency) through a system, network, or among entities.
-
C.
circulatesIn
Indicates that something moves or flows repeatedly within a particular space, system, or medium.
-
D.
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).
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
- F. None of above. chosen
Provenance (4 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.