Triple
T29298029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joinvilleaceae |
E742883
|
entity |
| Predicate | taxonomicAuthorityAbbreviation |
P30327
|
FINISHED |
| Object | Engl. |
—
|
NE NERFINISHED |
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: Engl. | Statement: [Joinvilleaceae, taxonomicAuthorityAbbreviation, Engl.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicAuthorityAbbreviation Context triple: [Joinvilleaceae, taxonomicAuthorityAbbreviation, Engl.]
-
A.
taxonomicAuthority
Indicates the entity that formally described, named, or classified another entity in a taxonomic context.
-
B.
taxonAbbreviation
Indicates that one taxonomic entity is associated with a standardized abbreviated form of its scientific name.
-
C.
scientificNameAbbreviation
Indicates that one entity is an abbreviated or shortened form of the scientific name of another entity.
-
D.
botanicalAuthorAbbreviation
chosen
Indicates the standardized abbreviated form of a botanist’s name used to cite them as the author of a plant’s scientific name.
-
E.
authorAbbreviation
Indicates that one entity is the standardized abbreviated form of an author's name used in citations or references for another entity.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654594048190ad15dbcd2c16db2e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:08 p.m.