Triple
T7952936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maluridae |
E184658
|
entity |
| Predicate | typicalSpeciesCommonName |
P77570
|
FINISHED |
| Object | superb fairywren |
—
|
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: superb fairywren | Statement: [Maluridae, typicalSpeciesCommonName, superb fairywren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeciesCommonName Context triple: [Maluridae, typicalSpeciesCommonName, superb fairywren]
-
A.
lessCommonSpecies
Indicates that one species is less common or less frequently observed than another species within a given context or environment.
-
B.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
C.
includesSpeciesCommonName
chosen
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
D.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
E.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5e51c88190abcc0534723e3660 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:10 p.m.