Triple
T36253467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blockbuster Video |
E891862
|
entity |
| Predicate | survivingStoreLocation |
P88578
|
FINISHED |
| Object | Bend, Oregon |
—
|
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: Bend, Oregon | Statement: [Blockbuster Video, survivingStoreLocation, Bend, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingStoreLocation Context triple: [Blockbuster Video, survivingStoreLocation, Bend, Oregon]
-
A.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
B.
placeOfEventSurvived
Indicates the location where an event occurred from which the subject successfully survived.
-
C.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
locationOfSurvivingUnit
chosen
Indicates the place where a remaining or still-active unit is currently situated.
-
E.
reserveLocation
Indicates that an entity designates or sets aside a specific place for a particular use, purpose, or future activity.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.