Triple
T37805304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zer0 Sum |
E942483
|
entity |
| Predicate | hasEpisodeTitleStyle |
P149910
|
FINISHED |
| Object | pun on the term zero-sum |
—
|
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: pun on the term zero-sum | Statement: [Zer0 Sum, hasEpisodeTitleStyle, pun on the term zero-sum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpisodeTitleStyle Context triple: [Zer0 Sum, hasEpisodeTitleStyle, pun on the term zero-sum]
-
A.
episodeTitle
Indicates that a given title string is the name of a specific episode within a series or program.
-
B.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
C.
styleOfTitle
chosen
Indicates the stylistic form or presentation type applied to a title (e.g., how the title is formatted or expressed).
-
D.
hasAlternativeTitleStyle
Indicates that an entity is associated with an alternative stylistic form or variation of its title.
-
E.
includesTitleStyle
Indicates that one entity incorporates or specifies a particular style or formatting for a title associated with it.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.