Triple
T31552783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swainson, 1839 |
E805048
|
entity |
| Predicate | taxonCommonNameGroup |
P168444
|
FINISHED |
| Object | loaches |
—
|
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: loaches | Statement: [Swainson, 1839, taxonCommonNameGroup, loaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonCommonNameGroup Context triple: [Swainson, 1839, taxonCommonNameGroup, loaches]
-
A.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
B.
taxonCommonName
chosen
Indicates that a taxonomic entity is associated with a common (vernacular) name used in everyday language.
-
C.
describedTaxonCommonName
Indicates that a taxon is being described or referenced using its common (vernacular) name rather than its scientific name.
-
D.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
E.
commonNameOfGenus
Indicates that the object is a commonly used name referring to the genus specified by the subject.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:11 p.m.