Triple
T33576830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stomp |
E860049
|
entity |
| Predicate | notableRunLocation |
—
|
GENERATED |
| Object | London |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRunLocation Context triple: [Stomp, notableRunLocation, London]
-
A.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableShowLocation
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
-
C.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
D.
notableAsSettingOf
Indicates that a place or environment is recognized as the setting where the events of a particular work (e.g., book, film, story) take place.
-
E.
notableLandRun
chosen
Indicates that a land run event is historically notable or significant in some recognized way.
- F. None of above.
Provenance (1 batch)
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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.