Triple
T25589984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmed Deedat |
E641493
|
entity |
| Predicate | notableDebateOpponent |
P64392
|
FINISHED |
| Object | Jimmy Swaggart |
—
|
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: Jimmy Swaggart | Statement: [Ahmed Deedat, notableDebateOpponent, Jimmy Swaggart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDebateOpponent Context triple: [Ahmed Deedat, notableDebateOpponent, Jimmy Swaggart]
-
A.
hasDebatedPerson
chosen
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
B.
notableOpponentIdeology
Indicates that an entity’s notable opponent is associated with, represents, or is characterized by a particular ideology.
-
C.
notablePolitician
Indicates that the subject is a politician who is recognized as notable or significant in a political context.
-
D.
notableProponent
Indicates that an entity is a well-known advocate or supporter of another entity, idea, or practice.
-
E.
notableOfficeHolder
Indicates that an entity is a significant or distinguished holder of a particular office or position associated with another entity.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 21, 2026, 4:19 p.m.