Triple
T18173456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keeping Up with the Randalls |
E435089
|
entity |
| Predicate | storyOutcomeType |
P40708
|
FINISHED |
| Object | comic resolution |
—
|
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: comic resolution | Statement: [Keeping Up with the Randalls, storyOutcomeType, comic resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyOutcomeType Context triple: [Keeping Up with the Randalls, storyOutcomeType, comic resolution]
-
A.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
B.
fictionalOutcome
Indicates that an event, action, or situation leads to a result that occurs only within a fictional, imagined, or non-real context.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
E.
narrativeConsequence
chosen
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df583a8081908c07d3534091c2ae |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.