Triple
T33576830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stomp |
E860049
|
entity |
| Predicate | notableRunLocation |
P73364
|
FINISHED |
| Object | London |
E1817
|
NE 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: London | Statement: [Stomp, notableRunLocation, London]
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 (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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a361182cd04819098962ef3a717f658 |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.