Triple
T2614203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basellaceae |
E58847
|
entity |
| Predicate | hasSucculentMembers |
P41434
|
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: [Basellaceae, hasSucculentMembers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSucculentMembers Context triple: [Basellaceae, hasSucculentMembers, true]
-
A.
isSeedPlant
Indicates that an entity is a plant that reproduces via seeds rather than spores or other methods.
-
B.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
C.
hasSporophyteCharacteristic
Indicates that an entity possesses a characteristic or trait associated with the sporophyte stage of a life cycle.
-
D.
hasBotanicalResource
Indicates that an entity possesses, contains, or is associated with a plant-based resource (such as plants, plant parts, or botanical materials) used for some purpose.
-
E.
plantCollection
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:50 p.m.