Triple
T29563063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Lulu |
E750087
|
entity |
| Predicate | victimOrder |
P169317
|
FINISHED |
| Object | second Rashidun caliph |
—
|
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: second Rashidun caliph | Statement: [Abu Lulu, victimOrder, second Rashidun caliph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimOrder Context triple: [Abu Lulu, victimOrder, second Rashidun caliph]
-
A.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
B.
victimParty
Indicates that one party is the victim or harmed side in an event, action, or situation involving another party.
-
C.
victimSide
Indicates that one entity is on, represents, or corresponds to the side of the victim in a conflict, incident, or harmful event.
-
D.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
E.
victimHeirTo
Indicates that the victim is the legal heir or inheritor of another person involved in the event or relationship.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 5:21 p.m.