Triple
T32668066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbrella Girl |
E835211
|
entity |
| Predicate | illustratedAs |
P174780
|
FINISHED |
| Object | wearing a yellow dress |
—
|
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: wearing a yellow dress | Statement: [Umbrella Girl, illustratedAs, wearing a yellow dress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illustratedAs Context triple: [Umbrella Girl, illustratedAs, wearing a yellow dress]
-
A.
oftenIllustratedBy
Indicates that something is frequently depicted, represented, or exemplified through a particular image, example, or illustration.
-
B.
hasIllustrations
Indicates that an entity includes or is accompanied by visual illustrations.
-
C.
hasIllustrationsBy
Indicates that one entity (such as a work or publication) includes illustrations that were created by another entity (the illustrator).
-
D.
genreIllustrated
Indicates that one entity is a genre that is exemplified or visually represented by the other entity.
-
E.
hasNotableIllustrationsOf
Indicates that something contains or features particularly significant or noteworthy illustrations depicting another entity or subject.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e32ec08190b74856937c4a9fc3 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:08 a.m.