Triple
T30871999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel One-Shot: A Funny Thing Happened on the Way to Thor’s Hammer |
E786365
|
entity |
| Predicate | followsEventsBefore |
P11018
|
FINISHED |
| Object | Thor |
—
|
NE NERFINISHED |
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: Thor | Statement: [Marvel One-Shot: A Funny Thing Happened on the Way to Thor’s Hammer, followsEventsBefore, Thor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsEventsBefore Context triple: [Marvel One-Shot: A Funny Thing Happened on the Way to Thor’s Hammer, followsEventsBefore, Thor]
-
A.
hasPrecedingEvents
chosen
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
B.
coversEventsAfter
Indicates that one event or time interval extends to include all events occurring after a specified reference event or time.
-
C.
plannedBeforeEvent
Indicates that one event or action was planned or scheduled to occur prior to a specified reference event.
-
D.
hasFormerEvent
Indicates that an entity was preceded by a specific earlier event in its history or sequence.
-
E.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 29, 2026, 8:48 p.m.