Triple
T72507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plantae |
E1451
|
entity |
| Predicate | lifeCycleFeature |
P642
|
FINISHED |
| Object | alternation of generations |
—
|
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: alternation of generations | Statement: [Plantae, lifeCycleFeature, alternation of generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeCycleFeature Context triple: [Plantae, lifeCycleFeature, alternation of generations]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsLife
Indicates that one entity provides conditions or resources that allow another entity to live, grow, or remain biologically viable.
-
C.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
D.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
E.
hasNotableFeature
chosen
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.