Triple
T25441198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udharbond Assembly constituency |
E637510
|
entity |
| Predicate | administrativeHeadquartersNearby |
P34698
|
FINISHED |
| Object | Silchar |
—
|
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: Silchar | Statement: [Udharbond Assembly constituency, administrativeHeadquartersNearby, Silchar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeHeadquartersNearby Context triple: [Udharbond Assembly constituency, administrativeHeadquartersNearby, Silchar]
-
A.
administrativeCentreNearby
chosen
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
-
B.
nearHeadquartersOf
Indicates that one entity is located geographically close to the headquarters of another entity.
-
C.
nearestDistrictHeadquarters
Indicates that one location is the closest district headquarters to another specified place.
-
D.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
E.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 2 p.m.