Triple
T18806163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munchausen syndrome by proxy |
E459878
|
entity |
| Predicate | typicalVictimAwareness |
P2764
|
FINISHED |
| Object | victim often unaware of fabrication |
—
|
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: victim often unaware of fabrication | Statement: [Munchausen syndrome by proxy, typicalVictimAwareness, victim often unaware of fabrication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVictimAwareness Context triple: [Munchausen syndrome by proxy, typicalVictimAwareness, victim often unaware of fabrication]
-
A.
awareness
chosen
Indicates that an entity has conscious knowledge, perception, or understanding of another entity, situation, or fact.
-
B.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
C.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
-
D.
typeOfVictimization
Indicates the specific kind or category of harmful act, abuse, or exploitation experienced by a victim.
-
E.
victimGroupHelped
Indicates that assistance, support, or aid was provided to a group identified as victims.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d7f8d08190a3e02fab6dc40bb5 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.