Triple
T26450286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taphrinomycotina |
E665328
|
entity |
| Predicate | isSisterGroupTo |
P5990
|
FINISHED |
| Object | Saccharomycotina |
—
|
NE NERFINISHED |
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: Saccharomycotina | Statement: [Taphrinomycotina, isSisterGroupTo, Saccharomycotina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSisterGroupTo Context triple: [Taphrinomycotina, isSisterGroupTo, Saccharomycotina]
-
A.
sisterGroup
chosen
Indicates that two groups share an immediate common ancestor in a hierarchy or classification, making them each other’s closest related group.
-
B.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
C.
isSupergroupOf
Indicates that one group contains another group as a proper subgroup, having strictly more members or elements than the other.
-
D.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
-
E.
isStructureGroupOf
Indicates that one entity functions as the structural grouping or organizing framework that encompasses or defines the structure 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612654a58819092a3b266c5f23ccf |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:05 a.m.