Triple
T11335196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagar Palika |
E268452
|
entity |
| Predicate | englishEquivalent |
P31361
|
FINISHED |
| Object | Municipality |
—
|
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: Municipality | Statement: [Nagar Palika, englishEquivalent, Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: englishEquivalent Context triple: [Nagar Palika, englishEquivalent, Municipality]
-
A.
EnglishTranslation
chosen
Indicates that one expression is the English-language translation equivalent of another expression.
-
B.
languageEquivalent
Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
-
C.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
D.
EnglishObjective
Indicates that an entity has English language proficiency or achievement as a goal or target to be attained.
-
E.
englishFlagship
Indicates that an entity participates in or is associated with an English flagship program (typically an intensive, advanced English language or studies track).
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.