Triple
T7175069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand von Mueller |
E167298
|
entity |
| Predicate | describedTaxa |
P20721
|
FINISHED |
| Object | many new Australian plant species |
—
|
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: many new Australian plant species | Statement: [Ferdinand von Mueller, describedTaxa, many new Australian plant species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedTaxa Context triple: [Ferdinand von Mueller, describedTaxa, many new Australian plant species]
-
A.
describedTaxon
chosen
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
B.
speciesDescription
Indicates a textual description that characterizes or explains the features, traits, or nature of a species.
-
C.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
D.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
E.
officiallyDescribedAs
Indicates that an entity is formally characterized or defined using a specific description in an official or authoritative context.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:48 p.m.