Triple
T35945240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setchellanthaceae |
E1039569
|
entity |
| Predicate | phylumOrDivision |
P34103
|
FINISHED |
| Object | Magnoliophyta |
—
|
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: Magnoliophyta | Statement: [Setchellanthaceae, phylumOrDivision, Magnoliophyta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phylumOrDivision Context triple: [Setchellanthaceae, phylumOrDivision, Magnoliophyta]
-
A.
phylum
Indicates that one entity belongs to, or is classified within, the biological phylum represented by the other entity.
-
B.
hasPhylum
chosen
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
-
C.
infraphylum
Indicates a taxonomic relationship where one entity is classified as an infraphylum, a rank directly below a subphylum and above a superclass, within the biological hierarchy of another entity.
-
D.
taxonomicDomain
Indicates that one entity is the biological taxonomic domain to which the other entity belongs.
-
E.
superphylum
Indicates that one taxonomic group is a superphylum that encompasses and ranks above another phylum-level group in biological classification.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.