Triple
T20754458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junco |
E510809
|
entity |
| Predicate | hasPlumageCharacteristic |
P4572
|
FINISHED |
| Object | often shows contrasting dark hood and paler underparts |
—
|
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: often shows contrasting dark hood and paler underparts | Statement: [Junco, hasPlumageCharacteristic, often shows contrasting dark hood and paler underparts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlumageCharacteristic Context triple: [Junco, hasPlumageCharacteristic, often shows contrasting dark hood and paler underparts]
-
A.
plumageFeature
chosen
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
B.
hasPrimaryPlumageColor
Indicates that an entity’s main or most dominant plumage (feather) color is a specified color.
-
C.
femalePlumageFeature
Indicates that the specified plumage feature is characteristic of the female individual in a species.
-
D.
plumageMarkingsColor
Indicates the color of the markings or patterns present on an entity's plumage.
-
E.
plumageColorCommon
Indicates that two entities share the same typical or most frequently observed plumage color.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22e0d288190ba924423af59d70d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:34 p.m.