Triple
T23139733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruwenzori turaco |
E577425
|
entity |
| Predicate | hasFeatherPigment |
P109796
|
FINISHED |
| Object | turacoverdin |
—
|
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: turacoverdin | Statement: [Ruwenzori turaco, hasFeatherPigment, turacoverdin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatherPigment Context triple: [Ruwenzori turaco, hasFeatherPigment, turacoverdin]
-
A.
hasPigment
chosen
Indicates that one entity contains, incorporates, or is characterized by a particular pigment.
-
B.
hasIridescentWings
Indicates that an entity possesses wings that display iridescence, showing changing colors when viewed from different angles.
-
C.
hasFleshColor
Indicates that an entity possesses a particular color or characteristic of its flesh or internal tissue.
-
D.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
E.
hasPrimaryPlumageColor
Indicates that an entity’s main or most dominant plumage (feather) color is a specified 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8e23988190814524f63a7efe36 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.