Triple
T580508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirachmaceae |
E15045
|
entity |
| Predicate | rarityStatus |
P7075
|
FINISHED |
| Object | rare |
—
|
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: rare | Statement: [Dirachmaceae, rarityStatus, rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rarityStatus Context triple: [Dirachmaceae, rarityStatus, rare]
-
A.
rarity
chosen
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
catalogueStatus
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
-
C.
collectionStrength
Indicates the degree or intensity of association or cohesion among items within a collection.
-
D.
statusOfHighDenominations
Indicates the current condition, availability, or regulatory standing of high-denomination units (such as large-value currency or instruments) within a system or context.
-
E.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b82b5248190ac863407e8207a3b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.