Triple
T9169858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDR |
E220054
|
entity |
| Predicate | usesAcronym |
P43
|
FINISHED |
| Object | HDI |
E42733
|
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: HDI | Statement: [HDR, usesAcronym, HDI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HDI Context triple: [HDR, usesAcronym, HDI]
-
A.
HDI
chosen
The HDI is a composite statistic used by the United Nations to measure and compare countries’ overall human development based on health, education, and standard of living.
-
B.
HCD
HCD is the California state agency responsible for housing policy, affordable housing programs, and community development initiatives.
-
C.
HCD
HCD is the common abbreviation for HC Davos, a professional ice hockey club based in Davos, Switzerland.
-
D.
HDX
HDX is an open humanitarian data platform that enables organizations to share, find, and use data for crisis preparedness and response.
-
E.
HDS
HDS is a high-dispersion spectrograph used on the Subaru Telescope for detailed spectroscopic studies of astronomical objects.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae23f048190847f12317be925b1 |
completed | April 1, 2026, 5:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0549746b0819099c2a591900f9c8c |
completed | April 4, 2026, midnight |
Created at: March 30, 2026, 7:22 p.m.