Triple
T18844690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swachh Survekshan |
E460885
|
entity |
| Predicate | rankingOutput |
P103031
|
FINISHED |
| Object | city cleanliness rankings |
—
|
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: city cleanliness rankings | Statement: [Swachh Survekshan, rankingOutput, city cleanliness rankings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingOutput Context triple: [Swachh Survekshan, rankingOutput, city cleanliness rankings]
-
A.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
B.
rankExamples
Indicates that one entity orders or scores a set of examples relative to each other, typically by relevance, quality, or importance.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
E.
rankingPositions
chosen
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ed944c81908592f0c34e5727a0 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.