Triple
T2661237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta vulgaris |
E54729
|
entity |
| Predicate | hasWildAncestor |
P369
|
FINISHED |
| Object | Beta vulgaris subsp. maritima |
—
|
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: Beta vulgaris subsp. maritima | Statement: [Beta vulgaris, hasWildAncestor, Beta vulgaris subsp. maritima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildAncestor Context triple: [Beta vulgaris, hasWildAncestor, Beta vulgaris subsp. maritima]
-
A.
hasAncestor
chosen
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
B.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
C.
hasExtinctBranch
Indicates that an entity has at least one branch, lineage, or subdivision that no longer exists (is extinct).
-
D.
hasNotableDescendant
Indicates that an entity has at least one descendant who is recognized as notable or significant in some context.
-
E.
hasLivingParent
Indicates that an entity has at least one parent who is currently alive.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.