Triple
T35163074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Montgomery |
E1015321
|
entity |
| Predicate | houseOwnerOf |
P119713
|
FINISHED |
| Object | Murder House |
—
|
NE NERFINISHED |
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: Murder House | Statement: [Charles Montgomery, houseOwnerOf, Murder House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseOwnerOf Context triple: [Charles Montgomery, houseOwnerOf, Murder House]
-
A.
houseOwnerInStory
chosen
Indicates that one entity is the owner of a house within the context or events of a particular story.
-
B.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
-
C.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
D.
houseHead
Indicates that one entity serves as the head, leader, or primary authority of a particular house or household associated with the other entity.
-
E.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.