Triple
T11017190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dunlin |
E260392
|
entity |
| Predicate | recognizedSubspecies |
P43004
|
FINISHED |
| Object | multiple geographic subspecies |
—
|
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: multiple geographic subspecies | Statement: [dunlin, recognizedSubspecies, multiple geographic subspecies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedSubspecies Context triple: [dunlin, recognizedSubspecies, multiple geographic subspecies]
-
A.
recognizedSubspeciesCount
chosen
Indicates the number of subspecies that are formally recognized for a given species or taxon.
-
B.
subspeciesOf
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
C.
hasEndemicSubspecies
Indicates that a species has one or more subspecies that are native and restricted to a particular geographic area.
-
D.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
E.
hasExtinctSubspecies
Indicates that an entity has at least one subspecies that is extinct.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a682908190b061d1995e2866b6 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.