Triple
T17874363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selyse Baratheon |
E446911
|
entity |
| Predicate | hairCondition |
P16252
|
FINISHED |
| Object | sparse facial 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: sparse facial hair | Statement: [Selyse Baratheon, hairCondition, sparse facial hair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairCondition Context triple: [Selyse Baratheon, hairCondition, sparse facial hair]
-
A.
hairType
Indicates the specific kind or category of hair an entity has, such as its texture, style, or structural type.
-
B.
hairDetail
chosen
Indicates a relationship that specifies particular characteristics or attributes of an entity’s hair, such as style, color, length, or texture.
-
C.
servesHairConcern
Indicates that a product, service, or action addresses or is intended to treat a specific hair-related concern.
-
D.
hasHair
Indicates that an entity possesses hair as a physical attribute.
-
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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa54d1481908c0af8533edd51c4 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:18 a.m.