Triple
T31756586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayanna Pressley |
E810568
|
entity |
| Predicate | has hair condition |
P172514
|
FINISHED |
| Object | alopecia |
—
|
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: alopecia | Statement: [Ayanna Pressley, has hair condition, alopecia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has hair condition Context triple: [Ayanna Pressley, has hair condition, alopecia]
-
A.
hasHair
Indicates that an entity possesses hair as a physical attribute.
-
B.
hairType
Indicates the specific kind or category of hair an entity has, such as its texture, style, or structural type.
-
C.
servesHairConcern
Indicates that a product, service, or action addresses or is intended to treat a specific hair-related concern.
-
D.
hairSpecialty
Indicates a professional focus or expertise in working with a particular type, style, or treatment of hair.
-
E.
hairDetail
Indicates a relationship that specifies particular characteristics or attributes of an entity’s hair, such as style, color, length, or texture.
- F. None of above. chosen
Provenance (4 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:29 p.m.