Triple
T2183882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genera Plantarum |
E49106
|
entity |
| Predicate | catalogues |
P20407
|
FINISHED |
| Object | vascular plant genera |
—
|
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: vascular plant genera | Statement: [Genera Plantarum, catalogues, vascular plant genera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogues Context triple: [Genera Plantarum, catalogues, vascular plant genera]
-
A.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
B.
catalog
chosen
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
C.
catalogueStatus
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
-
D.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.