Triple
T28859642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | three-domain system of Carl Woese |
E728822
|
entity |
| Predicate | domainRankAbove |
P165672
|
FINISHED |
| Object | phylum |
—
|
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: phylum | Statement: [three-domain system of Carl Woese, domainRankAbove, phylum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainRankAbove Context triple: [three-domain system of Carl Woese, domainRankAbove, phylum]
-
A.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
B.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
C.
rankingAuthority
Indicates that one entity serves as the official source or body responsible for assigning rankings or ordered evaluations to another entity.
-
D.
organRank
Indicates a hierarchical or priority ordering among organs relative to one another.
-
E.
hasRankingDomain
Indicates that one entity is associated with a specific ranking domain within which its rank or position is evaluated.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a15e4c48190bcba6a5e930e2a9e |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:46 a.m.