Triple
T38434014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Hanifa |
E903884
|
entity |
| Predicate | hadNotableLeader |
P77600
|
FINISHED |
| Object | Musaylima |
—
|
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: Musaylima | Statement: [Banu Hanifa, hadNotableLeader, Musaylima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNotableLeader Context triple: [Banu Hanifa, hadNotableLeader, Musaylima]
-
A.
hasFormerLeader
Indicates that an entity previously held the role of leader of another entity but no longer does.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
hasNotableNativeLeader
Indicates that an entity has a prominent or historically significant leader who is native to that entity’s own group, region, or community.
-
D.
hasProminentLeaderFromState
Indicates that an entity has a leading or highly influential figure whose origin or primary affiliation is with a specified state.
-
E.
hadPrincipalLeader
chosen
Indicates that an entity was led or headed by a primary or chief leader.
- 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.