Triple
T37595902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10050 Cielo Drive |
E935384
|
entity |
| Predicate | notableEventPerpetrator |
P153722
|
FINISHED |
| Object | Manson Family |
E2168619
|
NE 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: Manson Family | Statement: [10050 Cielo Drive, notableEventPerpetrator, Manson Family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventPerpetrator Context triple: [10050 Cielo Drive, notableEventPerpetrator, Manson Family]
-
A.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
B.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
C.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
D.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
E.
bearerNotableEvent
chosen
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
- F. None of above.
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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40e066fbb081909ae91b3854d16fd0 |
completed | June 28, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.