Triple
T32191775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janet Tyler |
E822274
|
entity |
| Predicate | hasDisfigurementStatus |
P196956
|
FINISHED |
| Object | considered disfigured by her society |
—
|
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: considered disfigured by her society | Statement: [Janet Tyler, hasDisfigurementStatus, considered disfigured by her society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisfigurementStatus Context triple: [Janet Tyler, hasDisfigurementStatus, considered disfigured by her society]
-
A.
hasDisfiguredHero
Indicates that a work features a hero character who is physically disfigured.
-
B.
faceDisfigurement
Indicates that an entity has a noticeable alteration or damage to the normal appearance or structure of its face.
-
C.
hasDeformation
Indicates that one entity exhibits or is characterized by a physical or structural deformation associated with another entity or condition.
-
D.
hasImpairmentStatus
Indicates that an entity possesses a particular condition of functional limitation, disability, or impairment status.
-
E.
hasScar
Indicates that one entity bears or possesses a scar 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 1, 2026, 12:35 a.m.