Triple
T14490464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himachal Pradesh High Court |
E359346
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | HPHC |
E359346
|
NE 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: HPHC | Statement: [Himachal Pradesh High Court, abbreviation, HPHC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HPHC Context triple: [Himachal Pradesh High Court, abbreviation, HPHC]
-
A.
HPHC
chosen
HPHC is the commonly used abbreviation for the Himachal Pradesh High Court, the highest judicial authority in the Indian state of Himachal Pradesh.
-
B.
PHC
PHC is the IATA airport code for Port Harcourt International Airport in Rivers State, Nigeria.
-
C.
PHC
PHC is the commonly used abbreviation for the Patna High Court, the high court of the Indian state of Bihar.
-
D.
HIP
HIP is a C++ runtime and programming model developed by AMD that enables portable GPU-accelerated code across AMD and NVIDIA hardware.
-
E.
HIP
HIP is the vehicle registration code for the German district of Roth in the state of Bavaria.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d9334708190baa2f8094df3c09e |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:20 a.m.