Triple
T35807946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Judgment Day |
E1035151
|
entity |
| Predicate | hasFormerAssociate |
P112494
|
FINISHED |
| Object | JD McDonagh |
—
|
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: JD McDonagh | Statement: [The Judgment Day, hasFormerAssociate, JD McDonagh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerAssociate Context triple: [The Judgment Day, hasFormerAssociate, JD McDonagh]
-
A.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
-
B.
hasFormerParticipant
chosen
Indicates that an entity once participated in an activity, event, or organization but is no longer a current participant.
-
C.
hasFormerAffiliationOfLeader
Indicates that an entity was previously affiliated with the organization or group to which a specified leader once belonged or led.
-
D.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
-
E.
holderIsFormer
Indicates that the referenced holder previously had, but no longer has, the specified role, position, or status.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:06 p.m.