Triple
T24644733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Bara ibn Azib |
E610072
|
entity |
| Predicate | reportedTopic |
P157151
|
FINISHED |
| Object | events of the Hijrah |
—
|
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: events of the Hijrah | Statement: [Al-Bara ibn Azib, reportedTopic, events of the Hijrah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedTopic Context triple: [Al-Bara ibn Azib, reportedTopic, events of the Hijrah]
-
A.
reportedTopic
chosen
Indicates that a subject has reported, discussed, or provided information about a particular topic or issue.
-
B.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
-
C.
reportedAs
Indicates that one entity has been formally reported or flagged to another entity, typically as problematic, suspicious, or noteworthy.
-
D.
reportedOn
Indicates that one entity has provided an account, description, or coverage of another entity, typically as news, documentation, or an official report.
-
E.
reportsAs
Indicates that one entity formally reports information, status, or results to 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 2:33 a.m.