Triple
T35945396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capparales |
E1039574
|
entity |
| Predicate | isObsoleteTaxon |
P88548
|
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: [Capparales, isObsoleteTaxon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObsoleteTaxon Context triple: [Capparales, isObsoleteTaxon, true]
-
A.
isOldWorldTaxon
Indicates that the taxon occurs naturally in, or is primarily associated with, the Old World (e.g., Europe, Asia, and Africa) rather than the New World.
-
B.
isTaxon
Indicates that one entity is a biological taxonomic unit (such as a species, genus, or family) associated with or classifying another entity.
-
C.
isObsoleteFor
chosen
Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
-
D.
notableTaxonStatus
Indicates that a taxon holds a special or noteworthy status (such as conservation concern, endemism, or other significance) within a given context.
-
E.
recognizedAsDistinctTaxonBy
Indicates that one entity is formally acknowledged as a separate and distinct taxonomic unit by a specified authority or source.
- 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_69f76e24bbd0819096b837d35371639a |
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.