Triple
T31174192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Rigby |
E794694
|
entity |
| Predicate | perceptionByOthersInStory |
P147578
|
FINISHED |
| Object | feared as a witch |
—
|
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: feared as a witch | Statement: [Mother Rigby, perceptionByOthersInStory, feared as a witch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptionByOthersInStory Context triple: [Mother Rigby, perceptionByOthersInStory, feared as a witch]
-
A.
perceivedCharacter
chosen
Indicates how one entity subjectively views or interprets the traits, qualities, or persona of another entity.
-
B.
perceivedRole
Indicates the role or function that one entity is regarded or interpreted as having in relation to another, based on perception rather than objective status.
-
C.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
D.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
E.
typicalPerception
Indicates the usual or most common way an entity is perceived or experienced through the senses.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 9:07 p.m.