Triple
T33828262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm Gonna Be (500 Miles) |
E867018
|
entity |
| Predicate | usedAtEvents |
P194130
|
FINISHED |
| Object | sporting events |
—
|
LITERAL 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: sporting events | Statement: [I'm Gonna Be (500 Miles), usedAtEvents, sporting events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAtEvents Context triple: [I'm Gonna Be (500 Miles), usedAtEvents, sporting events]
-
A.
usedInPublicEvents
chosen
Indicates that something is employed or featured during public events or gatherings.
-
B.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
C.
tookPlaceAtEvent
Indicates that an action or occurrence happened during or in the context of a specific event.
-
D.
notableUseEvent
Indicates an event in which something is used in a way that is significant or noteworthy, distinguishing it from ordinary or routine use.
-
E.
oftenHeldAtEvent
Indicates that one type of thing frequently takes place or is conducted during a particular event.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 1:46 a.m.