Triple
T26514496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | सेवा भारती |
E669774
|
entity |
| Predicate | कार्य_क्षेत्र |
P111844
|
FINISHED |
| Object | शहरी झुग्गी बस्तियाँ |
—
|
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: शहरी झुग्गी बस्तियाँ | Statement: [सेवा भारती, कार्य_क्षेत्र, शहरी झुग्गी बस्तियाँ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: कार्य_क्षेत्र Context triple: [सेवा भारती, कार्य_क्षेत्र, शहरी झुग्गी बस्तियाँ]
-
A.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
B.
area of activity
chosen
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
E.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 1:22 a.m.