Triple
T14307753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrosh |
E354740
|
entity |
| Predicate | cultureFeature |
P66792
|
FINISHED |
| Object | brightly dyed hair |
—
|
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: brightly dyed hair | Statement: [Tyrosh, cultureFeature, brightly dyed hair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureFeature Context triple: [Tyrosh, cultureFeature, brightly dyed hair]
-
A.
cultureMedium
Indicates the substance or environment used to grow, maintain, or study a biological specimen or culture.
-
B.
culturalScene
Indicates a relationship where an entity is associated with, participates in, or characterizes a particular cultural environment, milieu, or set of cultural activities.
-
C.
cultureCharacteristic
chosen
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
D.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b156b0819083f2bd319deed1b6 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.