Triple
T9738266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitrosopumilus |
E236119
|
entity |
| Predicate | belongsToSuperphylum |
P34908
|
FINISHED |
| Object | TACK archaea |
—
|
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: TACK archaea | Statement: [Nitrosopumilus, belongsToSuperphylum, TACK archaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSuperphylum Context triple: [Nitrosopumilus, belongsToSuperphylum, TACK archaea]
-
A.
hasSubphylum
Indicates that one biological entity is classified as a subphylum within the broader taxonomic grouping of another entity.
-
B.
superphylum
Indicates that one taxonomic group is a superphylum that encompasses and ranks above another phylum-level group in biological classification.
-
C.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
-
D.
hasSubkingdom
Indicates that one biological kingdom is divided into, or associated with, a specific subkingdom as a subordinate taxonomic rank.
-
E.
taxonOf
chosen
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.