Triple
T28032245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lophorina |
E708303
|
entity |
| Predicate | hasIridescentColor |
P164016
|
FINISHED |
| Object | turquoise |
—
|
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: turquoise | Statement: [Lophorina, hasIridescentColor, turquoise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIridescentColor Context triple: [Lophorina, hasIridescentColor, turquoise]
-
A.
hasIridescentColor
chosen
Indicates that an entity exhibits a shimmering, color-changing appearance that varies with viewing angle or lighting.
-
B.
hasIridescentScales
Indicates that an entity possesses scales exhibiting iridescence, meaning their colors appear to change when viewed from different angles or lighting conditions.
-
C.
hasIridescentWings
Indicates that an entity possesses wings that display iridescence, showing changing colors when viewed from different angles.
-
D.
isColorful
Indicates that an entity possesses multiple or striking colors, giving it a vivid or visually varied appearance.
-
E.
sparklingColor
Indicates that one entity has a bright, glittering, or shimmering color appearance in relation to another or in a given context.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:17 p.m.