Triple
T12840986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Schmidt |
E307049
|
entity |
| Predicate | hasDisfigurement |
P75397
|
FINISHED |
| Object | red skull-like face |
—
|
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: red skull-like face | Statement: [Johann Schmidt, hasDisfigurement, red skull-like face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisfigurement Context triple: [Johann Schmidt, hasDisfigurement, red skull-like face]
-
A.
hasDeformation
chosen
Indicates that one entity exhibits or is characterized by a physical or structural deformation associated with another entity or condition.
-
B.
hasScar
Indicates that one entity bears or possesses a scar on its body.
-
C.
skinCharacteristic
Indicates a relationship where an entity is associated with a particular quality, feature, or condition of its skin.
-
D.
defacedWith
Indicates that one entity has been damaged, marred, or vandalized using another entity as the means or material of defacement.
-
E.
hasBodyImageIssue
Indicates that an entity experiences concerns, dissatisfaction, or negative perceptions about their own body or physical appearance.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:35 p.m.