Triple
T13235291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Birnam |
E315130
|
entity |
| Predicate | triesToHide |
P68419
|
FINISHED |
| Object | bottles of alcohol in his apartment |
—
|
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: bottles of alcohol in his apartment | Statement: [Don Birnam, triesToHide, bottles of alcohol in his apartment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesToHide Context triple: [Don Birnam, triesToHide, bottles of alcohol in his apartment]
-
A.
helpedHide
Indicates that one entity assisted another in concealing or keeping something or someone hidden.
-
B.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
C.
hiddenAt
chosen
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
D.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
E.
triedToAvoid
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d36bdf8819099949b1e0e6902d3 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.