Triple
T2252761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Species Plantarum |
E49651
|
entity |
| Predicate | catalogedGroup |
P20407
|
FINISHED |
| Object | flowering plants |
—
|
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: flowering plants | Statement: [Species Plantarum, catalogedGroup, flowering plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogedGroup Context triple: [Species Plantarum, catalogedGroup, flowering plants]
-
A.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
B.
labelGroup
Indicates that an entity is assigned to or associated with a particular group label used for categorization or organization.
-
C.
areSometimesGroupedWith
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
-
D.
catalog
chosen
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
E.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11eb2708190bc5a3d152a3bb133 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.