Triple
T30399397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Yao |
E773307
|
entity |
| Predicate | hairstyleTradition |
P114974
|
FINISHED |
| Object | distinctive women’s hairstyles |
—
|
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: distinctive women’s hairstyles | Statement: [Red Yao, hairstyleTradition, distinctive women’s hairstyles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairstyleTradition Context triple: [Red Yao, hairstyleTradition, distinctive women’s hairstyles]
-
A.
hasHairstyleTradition
chosen
Indicates a relationship where an entity follows, practices, or is associated with a particular traditional hairstyle.
-
B.
hairStyleInMedia
Indicates that a particular hairstyle is depicted or represented in a specific media work or context.
-
C.
haircutNamedAfter
Indicates that a particular hairstyle is named after a specific person, character, place, or other entity.
-
D.
hairStyleTrademark
Indicates that a particular hairstyle is legally protected or recognized as a trademark associated with an entity.
-
E.
hairAsSymbol
Indicates that hair functions as a symbolic element representing ideas, traits, or meanings beyond its literal physical presence.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861706248190a1133c8aa35580cf |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.