Triple
T1408960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Till Death Us Do Part |
E31759
|
entity |
| Predicate | targetOfControversy |
P1783
|
FINISHED |
| Object | use of racist language |
—
|
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: use of racist language | Statement: [Till Death Us Do Part, targetOfControversy, use of racist language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfControversy Context triple: [Till Death Us Do Part, targetOfControversy, use of racist language]
-
A.
locationOfControversy
Indicates the place or setting where a dispute, debate, or controversy occurs or is centered.
-
B.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
E.
titleContested
Indicates that the legitimacy or ownership of a title is disputed between parties.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3c10f44819085e1c4601423740d |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.