Triple
T25192880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Da Boom |
E630918
|
entity |
| Predicate | settingAfterEvent |
P158418
|
FINISHED |
| Object | post-apocalyptic Quahog |
—
|
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: post-apocalyptic Quahog | Statement: [Da Boom, settingAfterEvent, post-apocalyptic Quahog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingAfterEvent Context triple: [Da Boom, settingAfterEvent, post-apocalyptic Quahog]
-
A.
settingAfter
Indicates that one setting or configuration occurs or is applied after another in a sequence or order.
-
B.
setAfterEventsOf
Indicates that one event or state is positioned or scheduled to occur after the completion of one or more specified preceding events.
-
C.
settingEvoked
Indicates that a particular setting or environment brings about, suggests, or calls to mind a specific response, mood, or association.
-
D.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
E.
replacedAfterEvent
Indicates that one entity takes the place of another entity following a specified event or occurrence.
- F. None of above. chosen
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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e113b448190a53554695d9441b4 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 12:45 p.m.