Triple
T29019993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeplastida |
E737423
|
entity |
| Predicate | landPlantsDerivedFrom |
P165920
|
FINISHED |
| Object | streptophyte green algae |
—
|
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: streptophyte green algae | Statement: [Archaeplastida, landPlantsDerivedFrom, streptophyte green algae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landPlantsDerivedFrom Context triple: [Archaeplastida, landPlantsDerivedFrom, streptophyte green algae]
-
A.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
B.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
plantProduces
Indicates that a plant generates, creates, or yields a particular substance, structure, or product as a result of its biological processes.
-
D.
plantSource
Indicates that something originates from, is derived from, or is produced by a particular plant.
-
E.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66004da14819098b0fa2906521298 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:48 a.m.