Triple
T30776607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15 Blenheim Road |
E783689
|
entity |
| Predicate | clueLocation |
P76038
|
FINISHED |
| Object | site of evidence about Megan Hipwell’s disappearance |
—
|
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: site of evidence about Megan Hipwell’s disappearance | Statement: [15 Blenheim Road, clueLocation, site of evidence about Megan Hipwell’s disappearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clueLocation Context triple: [15 Blenheim Road, clueLocation, site of evidence about Megan Hipwell’s disappearance]
-
A.
deckLocation
Indicates the specific deck or level on which an entity is located within a multi-deck structure or vehicle.
-
B.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
C.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
D.
locationInPlay
Indicates that an entity is currently situated or active within the defined play area or game environment.
-
E.
unveiledLocation
Indicates that an entity has revealed or made known the location of another entity or object.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe1c4d881908f331699d11a3c3f |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.