Triple
T38186799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandoba Temple, Saswad |
E1005338
|
entity |
| Predicate | importantForCommunity |
P188921
|
FINISHED |
| Object | Dhangar community |
—
|
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: Dhangar community | Statement: [Khandoba Temple, Saswad, importantForCommunity, Dhangar community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantForCommunity Context triple: [Khandoba Temple, Saswad, importantForCommunity, Dhangar community]
-
A.
socialImportance
chosen
Indicates the degree to which something holds significance, influence, or priority within a social context or group.
-
B.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
C.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
D.
focusesOnCommunity
Indicates that the subject prioritizes and directs attention or effort toward the well-being, needs, or development of a community.
-
E.
coreCommunity
Indicates that an entity belongs to the central or most essential group within a larger community.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:29 p.m.