Triple
T31535773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mucuna pruriens |
E804595
|
entity |
| Predicate | effectOfPodHairs |
P183739
|
FINISHED |
| Object | intense itching on contact with skin |
—
|
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: intense itching on contact with skin | Statement: [Mucuna pruriens, effectOfPodHairs, intense itching on contact with skin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfPodHairs Context triple: [Mucuna pruriens, effectOfPodHairs, intense itching on contact with skin]
-
A.
hairDetail
Indicates a relationship that specifies particular characteristics or attributes of an entity’s hair, such as style, color, length, or texture.
-
B.
hasHair
Indicates that an entity possesses hair as a physical attribute.
-
C.
hasBowHairMaterial
Indicates that an entity’s hair bow is made from a specified material.
-
D.
hasFurType
Indicates that an entity possesses a specific kind or texture of fur.
-
E.
hasFur
Indicates that an entity possesses fur as a physical covering on its body.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 30, 2026, 10:03 p.m.