Triple
T2671264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asterids |
E55750
|
entity |
| Predicate | monophyletic |
P20484
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Asterids, monophyletic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monophyletic Context triple: [Asterids, monophyletic, true]
-
A.
isMonophyletic
chosen
Indicates that a group of organisms includes a common ancestor and all of its descendants, forming a single complete branch on the tree of life.
-
B.
monogeneric
Indicates that a taxonomic group (such as a family or subfamily) contains only a single genus.
-
C.
phylogeneticSupport
Indicates that one entity provides evidence or justification for the inferred evolutionary relationship or branching pattern of another entity in a phylogenetic context.
-
D.
phylogeneticMarker
Indicates that one entity serves as a genetic or molecular feature used to infer or represent the evolutionary relationships of another entity.
-
E.
coMonarch
Indicates a relationship where two or more individuals jointly hold the position and authority of monarch over the same realm or polity.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98e7d00819088398206fc7db477 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.