Triple
T26630117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plumette |
E668466
|
entity |
| Predicate | hasFeatherColorInEnchantedForm |
P4572
|
FINISHED |
| Object | white |
—
|
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: white | Statement: [Plumette, hasFeatherColorInEnchantedForm, white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatherColorInEnchantedForm Context triple: [Plumette, hasFeatherColorInEnchantedForm, white]
-
A.
hasIridescentScales
Indicates that an entity possesses scales exhibiting iridescence, meaning their colors appear to change when viewed from different angles or lighting conditions.
-
B.
plumageFeature
chosen
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
C.
hasPrimaryPlumageColor
Indicates that an entity’s main or most dominant plumage (feather) color is a specified color.
-
D.
hasIridescentWings
Indicates that an entity possesses wings that display iridescence, showing changing colors when viewed from different angles.
-
E.
plumageColorSource
Indicates the relationship by which the color of an entity’s plumage is derived from or attributed to a particular source.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:24 a.m.