Triple
T35596883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitarganj |
E1028656
|
entity |
| Predicate | administrativeDistrictHQ |
P193369
|
FINISHED |
| Object | Rudrapur |
—
|
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: Rudrapur | Statement: [Sitarganj, administrativeDistrictHQ, Rudrapur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeDistrictHQ Context triple: [Sitarganj, administrativeDistrictHQ, Rudrapur]
-
A.
administrativeHeadquarterTown
chosen
Indicates the town that serves as the administrative headquarters for a given entity, such as an organization or territorial unit.
-
B.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
C.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
-
D.
districtHeadquartersSince
Indicates the time from which a particular location has served as the administrative headquarters of a specified district.
-
E.
headquartersMunicipality
Indicates the municipality in which an organization’s main administrative headquarters is located.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:05 p.m.