Triple
T9248283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemios Ventouris Roussos |
E222252
|
entity |
| Predicate | hasSignatureOutfit |
P36462
|
FINISHED |
| Object | kaftan-style robes |
—
|
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: kaftan-style robes | Statement: [Artemios Ventouris Roussos, hasSignatureOutfit, kaftan-style robes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureOutfit Context triple: [Artemios Ventouris Roussos, hasSignatureOutfit, kaftan-style robes]
-
A.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
B.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from others.
-
C.
hasGarment
Indicates that one entity possesses, wears, or is associated with a particular garment.
-
D.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
E.
notableOutfit
chosen
Indicates that an entity is known for or associated with wearing a particular outfit or style of clothing.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05f6d62c8190a1e33f1854767b47 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.