Triple
T23629831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tablighi Jamaat |
E583574
|
entity |
| Predicate | hasCentralGathering |
P16368
|
FINISHED |
| Object | Bishwa Ijtema |
—
|
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: Bishwa Ijtema | Statement: [Tablighi Jamaat, hasCentralGathering, Bishwa Ijtema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralGathering Context triple: [Tablighi Jamaat, hasCentralGathering, Bishwa Ijtema]
-
A.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
B.
gatheringPlace
chosen
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
C.
hasCentralTownFeature
Indicates that a town possesses a specific central feature or focal element (such as a landmark, square, or facility) that characterizes its core area.
-
D.
hasCentralOrgan
Indicates that an entity possesses a primary or main organ that serves as a central functional or structural component.
-
E.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e71cac8190a3e1c04d7a5fffa1 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.