Triple
T29852535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgard archaea |
E758100
|
entity |
| Predicate | haveGenomeFeatures |
P167668
|
FINISHED |
| Object | eukaryotic signature proteins |
—
|
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: eukaryotic signature proteins | Statement: [Asgard archaea, haveGenomeFeatures, eukaryotic signature proteins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveGenomeFeatures Context triple: [Asgard archaea, haveGenomeFeatures, eukaryotic signature proteins]
-
A.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
B.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
C.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
D.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
E.
hasNumberOfFeaturesDescribed
Indicates that an entity is associated with a specific count of its features that have been described.
- F. None of above. chosen
Provenance (4 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_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:44 p.m.