Triple
T35924310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jussieua |
E1038976
|
entity |
| Predicate | isInClade |
P10936
|
FINISHED |
| Object | Angiosperms |
—
|
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: Angiosperms | Statement: [Jussieua, isInClade, Angiosperms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInClade Context triple: [Jussieua, isInClade, Angiosperms]
-
A.
belongsToClade
chosen
Indicates that an organism or taxonomic group is a member of, or included within, a specified evolutionary clade.
-
B.
recognizesClade
Indicates that one entity acknowledges or accepts another entity as a valid clade or monophyletic group in a classification or phylogenetic context.
-
C.
containsCladeLeadingTo
Indicates that one entity (typically a taxonomic group or node) includes within it the clade that leads to another specified entity in an evolutionary or hierarchical structure.
-
D.
extantSubclade
Indicates that one clade is a currently living (still existing) descendant subgroup within another clade.
-
E.
proposedClade
Indicates that one entity is hypothesized to form a clade with another (or others), representing a suggested but not necessarily confirmed evolutionary grouping.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
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.