Triple
T16572654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluth's Original Frozen Banana |
E402625
|
entity |
| Predicate | containsHidden |
P68420
|
FINISHED |
| Object | cash in the walls |
—
|
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: cash in the walls | Statement: [Bluth's Original Frozen Banana, containsHidden, cash in the walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHidden Context triple: [Bluth's Original Frozen Banana, containsHidden, cash in the walls]
-
A.
containsHiddenTrack
Indicates that one media item includes another track that is not immediately apparent or listed, such as a hidden or uncredited track on an album.
-
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.
hasHiddenImage
Indicates that an entity contains or is associated with an image that is not immediately visible or is intentionally concealed from normal view.
-
D.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
E.
dataHidden
Indicates that certain data is concealed, inaccessible, or not visible to users or systems under normal conditions.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35959f1748190934b263d6bc94143 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.