Triple
T29852553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgard archaea |
E758100
|
entity |
| Predicate | haveTypeGenus |
P5980
|
FINISHED |
| Object | Candidatus Lokiarchaeum |
—
|
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: Candidatus Lokiarchaeum | Statement: [Asgard archaea, haveTypeGenus, Candidatus Lokiarchaeum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTypeGenus Context triple: [Asgard archaea, haveTypeGenus, Candidatus Lokiarchaeum]
-
A.
hasTypeGenus
chosen
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
B.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
isTypeSpeciesOfGenus
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a particular genus.
-
D.
namedAfterTypeGenus
Indicates that an entity (such as a taxonomic group) is named after its type genus.
-
E.
genusIncludes
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67648f35c8190ab466e413b6dbcb5 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:44 p.m.