Triple
T33272491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nation of Islam mosques |
E851811
|
entity |
| Predicate | typicallyStaffedBy |
P127311
|
FINISHED |
| Object | Fruit of Islam |
E240698
|
NE 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: Fruit of Islam | Statement: [Nation of Islam mosques, typicallyStaffedBy, Fruit of Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyStaffedBy Context triple: [Nation of Islam mosques, typicallyStaffedBy, Fruit of Islam]
-
A.
staffMember
Indicates that one entity serves as an employee or staff member of another entity, such as an organization or institution.
-
B.
hasLocalStaffFrom
Indicates that an organization or entity employs or is staffed by people originating from a specified local area or region.
-
C.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
D.
hadStaffRole
Indicates that an entity served in a specific staff role or position for another entity during some period.
-
E.
usesStaffCategory
chosen
Indicates that an entity employs or applies a particular category or classification of staff in its operations or context.
- F. None of above.
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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3576d575508190b7dee5ae0d4696ec |
completed | June 19, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:32 a.m.