Triple
T22360592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horse Protection Act |
E552768
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | HPA |
—
|
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: HPA | Statement: [Horse Protection Act, abbreviation, HPA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HPA Context triple: [Horse Protection Act, abbreviation, HPA]
-
A.
HPA
chosen
HPA is the commonly used abbreviation for the Horse Protection Act, a U.S. federal law aimed at preventing the abusive practice of soring in show horses.
-
B.
HPA
HPA is the abbreviation for the Hamburg Port Authority, the organization responsible for managing and developing the Port of Hamburg in Germany.
-
C.
HPA
HPA is the station code for Hunterspoint Avenue, a Long Island Rail Road commuter rail station in Queens, New York City.
-
D.
HAP
HAP is Apple's HomeKit Accessory Protocol, a communication standard that defines how smart home accessories securely interact with Apple devices and the Home app.
-
E.
HPN
HPN is the IATA airport code for Westchester County Airport, a regional airport serving Westchester County, New York and the surrounding area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d3852c819082518851568e1b51 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 16, 2026, 8:44 p.m.