Triple
T3844900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reissekia |
E93544
|
entity |
| Predicate | belongsToBiologicalGroup |
P16820
|
FINISHED |
| Object | vascular plants |
—
|
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: vascular plants | Statement: [Reissekia, belongsToBiologicalGroup, vascular plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToBiologicalGroup Context triple: [Reissekia, belongsToBiologicalGroup, vascular plants]
-
A.
belongsToBiogeographicRealm
Indicates that an entity (such as a species, habitat, or location) is associated with or falls within a particular biogeographic realm.
-
B.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
C.
belongsToBiosyntheticFamily
Indicates that one biochemical compound or pathway is classified as part of a specific biosynthetic family based on its origin or synthesis route.
-
D.
belongsToClade
Indicates that an organism or taxonomic group is a member of, or included within, a specified evolutionary clade.
-
E.
taxonOf
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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb655c081909ec5ff3d09eb4778 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.