Triple
T29798877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 Wonderland Avenue murders |
E756632
|
entity |
| Predicate | householdInvolved |
P63314
|
FINISHED |
| Object | drug den |
—
|
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: drug den | Statement: [1981 Wonderland Avenue murders, householdInvolved, drug den]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdInvolved Context triple: [1981 Wonderland Avenue murders, householdInvolved, drug den]
-
A.
familyInvolvement
chosen
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
B.
houseInvolved
Indicates that a house plays a significant role or is directly implicated in the specified event, situation, or relationship.
-
C.
rightInvolved
Indicates that an entity is involved in or associated with a legal or formal right held, exercised, or affected in a given context.
-
D.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
E.
familyAffectedBy
Indicates that one or more members of a person’s family experience or are impacted by a specified condition, event, or circumstance.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 5:17 p.m.