Triple
T9971056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakata Gion Yamakasa |
E196203
|
entity |
| Predicate | participantClothing |
P42160
|
FINISHED |
| Object | happi coats |
—
|
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: happi coats | Statement: [Hakata Gion Yamakasa, participantClothing, happi coats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantClothing Context triple: [Hakata Gion Yamakasa, participantClothing, happi coats]
-
A.
coatCharacteristic
Indicates that one entity has a particular property, feature, or quality that characterizes its outer covering or surface.
-
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.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
D.
usesDressing
Indicates that one entity applies or employs a particular dressing (such as a sauce, covering, or treatment) in relation to another entity or context.
-
E.
hasGarment
chosen
Indicates that one entity possesses, wears, or is associated with a particular garment.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b96b1c8190b9d3c1171346615a |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.