Triple
T14307781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrosh |
E354740
|
entity |
| Predicate | hairCustom |
P16252
|
FINISHED |
| Object | men dye beards and mustaches |
—
|
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: men dye beards and mustaches | Statement: [Tyrosh, hairCustom, men dye beards and mustaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairCustom Context triple: [Tyrosh, hairCustom, men dye beards and mustaches]
-
A.
hairType
Indicates the specific kind or category of hair an entity has, such as its texture, style, or structural type.
-
B.
hairAsSymbol
Indicates that hair functions as a symbolic element representing ideas, traits, or meanings beyond its literal physical presence.
-
C.
hairDetail
chosen
Indicates a relationship that specifies particular characteristics or attributes of an entity’s hair, such as style, color, length, or texture.
-
D.
hairReplacedBy
Indicates that one entity’s hair has been substituted, covered, or superseded by another entity.
-
E.
hairCraftedBy
Indicates that a hairstyle or hair-related work was created or styled by a specific person or agent.
- 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.