Triple
T11489461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilith |
E272365
|
entity |
| Predicate | fearedFor |
P99766
|
FINISHED |
| Object | harming infants |
—
|
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: harming infants | Statement: [Lilith, fearedFor, harming infants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fearedFor Context triple: [Lilith, fearedFor, harming infants]
-
A.
notableFear
Indicates that one entity is especially afraid of, or has a significant fear related to, another entity.
-
B.
pursuedForCrime
Indicates that an entity is being actively sought or chased by authorities or others because of an alleged or committed crime.
-
C.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
D.
allegedVictimOf
Indicates that one entity is claimed or reported to have been harmed, wronged, or victimized by another entity, without asserting that the claim is proven.
-
E.
suspectedPerpetrator
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a20df608190992543b4d7006f8a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.