Triple
T22253758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilleniidae |
E550044
|
entity |
| Predicate | statusInModernSystems |
P144079
|
FINISHED |
| Object | largely obsolete |
—
|
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: largely obsolete | Statement: [Dilleniidae, statusInModernSystems, largely obsolete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInModernSystems Context triple: [Dilleniidae, statusInModernSystems, largely obsolete]
-
A.
statusInSystem7
Indicates that an entity holds a particular status or state within the context of system 7.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
legalStatusModern
Indicates the current legal standing or classification of an entity under contemporary law or regulatory frameworks.
-
D.
statusInModernUsage
chosen
Indicates how the usage or relevance of something is currently regarded or applied in contemporary contexts.
-
E.
statusInModernBiology
Indicates the recognized role, classification, or relevance that something holds within the framework of contemporary biological science.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c0c4f48190a75473a7835014f1 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.