Triple
T8188719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beale Street Blues |
E191250
|
entity |
| Predicate | setInFictionalOrRealLocation |
P81329
|
FINISHED |
| Object | Beale Avenue |
—
|
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: Beale Avenue | Statement: [Beale Street Blues, setInFictionalOrRealLocation, Beale Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInFictionalOrRealLocation Context triple: [Beale Street Blues, setInFictionalOrRealLocation, Beale Avenue]
-
A.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
B.
hasFictionalLocation
Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
-
C.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
D.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
E.
locatedInFictionalCountry
Indicates that an entity exists or is situated within a country that is fictional rather than real.
- F. None of above. chosen
Provenance (4 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4d9f4a488190b39bdc1792646914 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:41 p.m.