Triple
T26989129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Cunanan |
E679817
|
entity |
| Predicate | locatedInBodyOfWaterAtDeath |
P1714
|
FINISHED |
| Object | houseboat in Miami Beach |
—
|
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: houseboat in Miami Beach | Statement: [Andrew Cunanan, locatedInBodyOfWaterAtDeath, houseboat in Miami Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBodyOfWaterAtDeath Context triple: [Andrew Cunanan, locatedInBodyOfWaterAtDeath, houseboat in Miami Beach]
-
A.
locatedInBodyOfWater
chosen
Indicates that an entity is situated within or on the surface of a specific body of water.
-
B.
tookPlaceInBodyOfWater
Indicates that an event or action occurred within or on a specific body of water.
-
C.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
D.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
E.
locatedInBodyOfWaterSharedBy
Indicates that an entity is situated within a body of water that is shared by another specified entity.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 27, 2026, 6:50 a.m.