Triple
T12375625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munger |
E295114
|
entity |
| Predicate | hasDistrictHeadquarters |
P76475
|
FINISHED |
| Object | Munger district headquarters |
—
|
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: Munger district headquarters | Statement: [Munger, hasDistrictHeadquarters, Munger district headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistrictHeadquarters Context triple: [Munger, hasDistrictHeadquarters, Munger district headquarters]
-
A.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
B.
districtHeadquartersSince
Indicates the time from which a particular location has served as the administrative headquarters of a specified district.
-
C.
nearestDistrictHeadquarters
Indicates that one location is the closest district headquarters to another specified place.
-
D.
districtHeadquartersLocation
chosen
Indicates the place where the administrative headquarters of a district is located.
-
E.
headquartersDistrict
Indicates the administrative district or area where an organization’s main 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fb8d6c081909e8bbbd52c73f29c |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.