Triple
T30568755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abby Brewster |
E778061
|
entity |
| Predicate | hidesBodiesIn |
P68420
|
FINISHED |
| Object | house cellar |
—
|
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: house cellar | Statement: [Abby Brewster, hidesBodiesIn, house cellar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hidesBodiesIn Context triple: [Abby Brewster, hidesBodiesIn, house cellar]
-
A.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
B.
hiddenIn
chosen
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
C.
obscuredIn
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
-
D.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
E.
canBecomeInvisible
Indicates the ability of an entity to transition from being visible to being unseen or undetectable.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689108d448190ba08a76cfaea85ce |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:21 p.m.