Triple
T27433500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatib ibn Abi Baltaah |
E690712
|
entity |
| Predicate | facedAccusationOf |
P86554
|
FINISHED |
| Object | betraying military secrets to Quraysh |
—
|
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: betraying military secrets to Quraysh | Statement: [Hatib ibn Abi Baltaah, facedAccusationOf, betraying military secrets to Quraysh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedAccusationOf Context triple: [Hatib ibn Abi Baltaah, facedAccusationOf, betraying military secrets to Quraysh]
-
A.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
B.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
C.
victimOfAccusation
chosen
Indicates that an entity is the target or subject of an accusation made by another party.
-
D.
associatedWithAccusation
Indicates a relationship where an entity is linked or connected to a specific accusation or charge.
-
E.
crimeAccusation
Indicates that one entity formally accuses another entity of having committed a crime.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 12:43 p.m.