Triple
T38434023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Hanifa |
E903884
|
entity |
| Predicate | hadReligiousMovement |
P17590
|
FINISHED |
| Object | Musaylima’s prophetic claim |
—
|
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: Musaylima’s prophetic claim | Statement: [Banu Hanifa, hadReligiousMovement, Musaylima’s prophetic claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadReligiousMovement Context triple: [Banu Hanifa, hadReligiousMovement, Musaylima’s prophetic claim]
-
A.
hasReligiousMovement
chosen
Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
-
B.
religiousMovementLed
Indicates that one entity serves as the leader or guiding figure of a particular religious movement.
-
C.
hadMajorReligion
Indicates that a particular religion was the primary or dominant faith practiced within a given entity (such as a region, state, or population) during a specified period.
-
D.
hasReligiousMovementTypeFoundedThere
Indicates that a particular religious movement was founded or originated at the referenced location.
-
E.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.