Triple
T29019990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeplastida |
E737423
|
entity |
| Predicate | includesLineages |
P196076
|
FINISHED |
| Object | freshwater species |
—
|
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: freshwater species | Statement: [Archaeplastida, includesLineages, freshwater species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLineages Context triple: [Archaeplastida, includesLineages, freshwater species]
-
A.
containsLineages
chosen
Indicates that one entity includes or encompasses one or more specified lineages within its scope or structure.
-
B.
impliesLineage
Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
-
C.
importantLineage
Indicates that one entity’s ancestry, heritage, or familial line is considered especially significant or influential in relation to another entity or context.
-
D.
hasLineageCharacteristic
Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
-
E.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
- 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_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: April 28, 2026, 9:48 a.m.