Triple
T32017112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Bunch |
E817573
|
entity |
| Predicate | usedHideout |
P43162
|
FINISHED |
| Object | Hole-in-the-Wall |
—
|
NE NERFINISHED |
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: Hole-in-the-Wall | Statement: [Wild Bunch, usedHideout, Hole-in-the-Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHideout Context triple: [Wild Bunch, usedHideout, Hole-in-the-Wall]
-
A.
hidingPlace
chosen
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
-
B.
wentIntoHiding
Indicates that an entity deliberately withdrew from public view or contact to avoid detection, attention, or danger.
-
C.
bunkerNowUsedAs
Indicates that a structure originally built as a bunker is currently being used for a different specified purpose.
-
D.
operatedHidingPlaceAt
Indicates that an entity managed or ran a particular hiding place at a specified time or during a certain period.
-
E.
outfallLocation
Indicates the geographic place where a discharge, such as wastewater or runoff, is released into the environment.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b43bac9881908cc2bfe063135df1 |
completed | May 3, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:16 a.m.