Triple
T4162822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qadiri |
E91570
|
entity |
| Predicate | hasCentralPractice |
P15354
|
FINISHED |
| Object | collective dhikr gatherings |
—
|
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: collective dhikr gatherings | Statement: [Qadiri, hasCentralPractice, collective dhikr gatherings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralPractice Context triple: [Qadiri, hasCentralPractice, collective dhikr gatherings]
-
A.
hasCentralAct
chosen
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
B.
hasCentralCounty
Indicates that an administrative or geographic region is associated with a specific county that serves as its central or primary county.
-
C.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by another entity.
-
D.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
E.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.