Triple
T12614051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | saio-dai |
E301205
|
entity |
| Predicate | wornClothingStyle |
P104877
|
FINISHED |
| Object | Heian-period court 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: Heian-period court robes | Statement: [saio-dai, wornClothingStyle, Heian-period court robes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wornClothingStyle Context triple: [saio-dai, wornClothingStyle, Heian-period court robes]
-
A.
fashionStyle
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
B.
typicallyWornBy
Indicates that something (such as an item or garment) is most commonly or characteristically worn by a particular type of person or group.
-
C.
typicalWear
chosen
Indicates that one entity is commonly or characteristically worn by the other in typical situations or contexts.
-
D.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
E.
fashionCharacteristic
Indicates a relationship where one entity possesses or exhibits a particular style, trend, or fashion-related attribute in relation to another.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.