Triple
T11387463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illudium Q-36 Explosive Space Modulator |
E269746
|
entity |
| Predicate | runningGagFunction |
P58285
|
FINISHED |
| Object | Marvin the Martian’s failed plans |
—
|
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: Marvin the Martian’s failed plans | Statement: [Illudium Q-36 Explosive Space Modulator, runningGagFunction, Marvin the Martian’s failed plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningGagFunction Context triple: [Illudium Q-36 Explosive Space Modulator, runningGagFunction, Marvin the Martian’s failed plans]
-
A.
featuresRunningGag
chosen
Indicates that the subject includes or makes use of a recurring joke or humorous motif.
-
B.
notableGag
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
-
C.
runsAround
Indicates that one entity moves in a circular or surrounding path around another entity or area.
-
D.
ranOn
Indicates that an entity executed or operated on a particular platform, system, or environment.
-
E.
runsFrom
Indicates that one entity flees or escapes away from another entity.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.