Triple
T34746916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitrastemonaceae |
E1001660
|
entity |
| Predicate | systematicsNotes |
P12461
|
FINISHED |
| Object | formerly placed in Rafflesiales by some authors |
—
|
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: formerly placed in Rafflesiales by some authors | Statement: [Mitrastemonaceae, systematicsNotes, formerly placed in Rafflesiales by some authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systematicsNotes Context triple: [Mitrastemonaceae, systematicsNotes, formerly placed in Rafflesiales by some authors]
-
A.
systematicsNote
chosen
Indicates that there is an associated comment or annotation concerning the classification or systematic arrangement of the entities involved.
-
B.
systematics
Indicates the relationship of organizing, classifying, and arranging entities into a structured system based on their characteristics or relationships.
-
C.
taxonomicHistory
Indicates the historical sequence of taxonomic classifications or changes that an entity has undergone over time.
-
D.
taxonType
Indicates the biological or taxonomic rank/category that characterizes a given taxon.
-
E.
usedTaxonomicSystem
Indicates that a particular taxonomic classification system was applied or followed when organizing or identifying the entities involved.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.