Triple
T29019979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeplastida |
E737423
|
entity |
| Predicate | primaryPlastidsDerivedFrom |
P110721
|
FINISHED |
| Object | single ancient endosymbiotic event |
—
|
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: single ancient endosymbiotic event | Statement: [Archaeplastida, primaryPlastidsDerivedFrom, single ancient endosymbiotic event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPlastidsDerivedFrom Context triple: [Archaeplastida, primaryPlastidsDerivedFrom, single ancient endosymbiotic event]
-
A.
plastidsType
Indicates the specific kind or category of plastids associated with an entity.
-
B.
chloroplastOrigin
chosen
Indicates that one entity is the evolutionary or developmental source from which the other entity’s chloroplasts are derived.
-
C.
chloroplastMorphology
Indicates the structural form, shape, and organization of chloroplasts in a cell.
-
D.
biotaDerivedFrom
Indicates that one biological entity originates from, or is derived from, another biological source or organism.
-
E.
plastidPigmentsInclude
Indicates that the set of pigments present in a plastid includes a specified pigment or group of pigments.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: April 28, 2026, 9:48 a.m.