Triple
T31018647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calamospiza melanocorys |
E790392
|
entity |
| Predicate | maleBreedingPlumageMarking |
P82321
|
FINISHED |
| Object | large white wing patch |
—
|
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: large white wing patch | Statement: [Calamospiza melanocorys, maleBreedingPlumageMarking, large white wing patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleBreedingPlumageMarking Context triple: [Calamospiza melanocorys, maleBreedingPlumageMarking, large white wing patch]
-
A.
maleBreedingPlumageFeature
chosen
Indicates that the relationship involves a physical or visual characteristic specifically associated with a male’s breeding-season plumage.
-
B.
malePlumage
Indicates that the specified plumage belongs to or characterizes the male individual of a species.
-
C.
plumageDimorphism
Indicates that there is a difference in plumage characteristics between two groups (typically sexes or age classes) within a species.
-
D.
wingColorMale
Indicates the color of the wings specifically for male individuals of a species.
-
E.
plumageMarkingsColor
Indicates the color of the markings or patterns present on an entity's plumage.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:58 p.m.