Triple
T21679040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironic |
E535051
|
entity |
| Predicate | hasParodyDebate |
P145420
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Ironic, hasParodyDebate, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParodyDebate Context triple: [Ironic, hasParodyDebate, Yes]
-
A.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
B.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
C.
hasDebateFormat
Indicates that a particular debate, event, or context uses or follows a specified debate format or structure.
-
D.
hasDebateStatus
Indicates that an entity (such as a topic, motion, or issue) is associated with a particular stage or condition within a debate process (e.g., proposed, ongoing, concluded).
-
E.
hasDebateParticipants
Indicates that a debate involves the specified participants as parties engaged in the discussion or argument.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a11ce548190aaff404aed6a76cd |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:43 p.m.