Triple
T20011170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wuggly Ump |
E494591
|
entity |
| Predicate | hasIllustrationTechnique |
P14965
|
FINISHED |
| Object | fine line cross-hatching |
—
|
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: fine line cross-hatching | Statement: [The Wuggly Ump, hasIllustrationTechnique, fine line cross-hatching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIllustrationTechnique Context triple: [The Wuggly Ump, hasIllustrationTechnique, fine line cross-hatching]
-
A.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
-
B.
hasIllustrationsBy
Indicates that one entity (such as a work or publication) includes illustrations that were created by another entity (the illustrator).
-
C.
hasIllustrations
Indicates that an entity includes or is accompanied by visual illustrations.
-
D.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
E.
hasNotableIllustrationsOf
Indicates that something contains or features particularly significant or noteworthy illustrations depicting another entity or subject.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662362df48190abf16129eea39985 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.