Triple
T29588183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dea |
E754080
|
entity |
| Predicate | cannotPerceive |
P165580
|
FINISHED |
| Object | Gwynplaine's disfigured 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: Gwynplaine's disfigured face | Statement: [Dea, cannotPerceive, Gwynplaine's disfigured face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotPerceive Context triple: [Dea, cannotPerceive, Gwynplaine's disfigured face]
-
A.
failsToPerceive
chosen
Indicates that an entity does not notice, detect, or become aware of another entity or event that is present or occurring.
-
B.
hasPerception
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
C.
cannot
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
D.
blind
Indicates that an entity lacks the ability to see, either partially or completely, resulting in an absence or severe limitation of visual perception.
-
E.
cannotExpress
Indicates that one entity is unable to convey, articulate, or communicate something (such as a feeling, idea, or message) to another entity.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 6:12 p.m.