Triple
T30346761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClariS |
E771886
|
entity |
| Predicate | imageConcept |
P169406
|
FINISHED |
| Object | illustrated avatars instead of public faces |
—
|
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: illustrated avatars instead of public faces | Statement: [ClariS, imageConcept, illustrated avatars instead of public faces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageConcept Context triple: [ClariS, imageConcept, illustrated avatars instead of public faces]
-
A.
imageOf
Indicates that one entity is a visual representation or depiction of another entity.
-
B.
imageDepictedWith
Indicates that one entity is visually represented together with another entity within the same image.
-
C.
evokesImageOf
Indicates that one entity triggers or brings to mind a mental image or visual representation of another entity.
-
D.
imageDepictedIn
Indicates that a particular image is shown, represented, or included within another resource or context.
-
E.
visualMetaphor
Indicates a relationship where one entity conceptually represents or explains another through a visual analogy or symbolic imagery.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682084db081909e261c5bbae024e3 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:56 p.m.