Triple
T36388609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaican hummingbird |
E896265
|
entity |
| Predicate | colorVision |
P188145
|
FINISHED |
| Object | can see ultraviolet patterns on flowers |
—
|
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: can see ultraviolet patterns on flowers | Statement: [Jamaican hummingbird, colorVision, can see ultraviolet patterns on flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorVision Context triple: [Jamaican hummingbird, colorVision, can see ultraviolet patterns on flowers]
-
A.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
B.
colorTheory
Indicates a relationship where principles or concepts about how colors interact, combine, or affect perception are applied or referenced between entities.
-
C.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
D.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
E.
colorDisplay
Indicates that one entity presents, shows, or renders the color associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:10 p.m.