Triple
T7347780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansar |
E169421
|
entity |
| Predicate | relationshipToMuhajirun |
P76718
|
FINISHED |
| Object | hosts |
—
|
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: hosts | Statement: [Ansar, relationshipToMuhajirun, hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMuhajirun Context triple: [Ansar, relationshipToMuhajirun, hosts]
-
A.
relationToUthman
Indicates the type of relationship or connection an entity has to Uthman.
-
B.
familyRelationInIslamicTradition
Indicates a familial relationship as defined within Islamic tradition, including kinship ties, marital bonds, and lineage-based connections governed by Islamic law and customs.
-
C.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
D.
relationToKhalidIbnAlWalid
Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
-
E.
relationshipToAllPalestineGovernment
Indicates the nature or type of relationship an entity has with the All-Palestine Government.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1379cac81908b35e617c44c7b13 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:05 p.m.