Triple
T17491992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve of Destruction |
E425945
|
entity |
| Predicate | bannedOnSomeRadioStations |
P72781
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eve of Destruction, bannedOnSomeRadioStations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedOnSomeRadioStations Context triple: [Eve of Destruction, bannedOnSomeRadioStations, true]
-
A.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
B.
bannedInCountry
Indicates that something is officially prohibited or not allowed within the jurisdiction of a specified country.
-
C.
bannedInContextOf
chosen
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
D.
onlyRegularBan'eiTrack
Indicates that the relationship holds when a horse race is conducted exclusively on a standard, non-special Ban'ei track configuration.
-
E.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d5dd5c8190a8631e0d2ca1e427 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.