Triple
T8828444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Hacker's Dictionary |
E210073
|
entity |
| Predicate | alternateTitle |
P39
|
FINISHED |
| Object | TNHD |
E210073
|
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: TNHD | Statement: [The New Hacker's Dictionary, alternateTitle, TNHD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TNHD Context triple: [The New Hacker's Dictionary, alternateTitle, TNHD]
-
A.
TNHD
chosen
TNHD is the commonly used abbreviation for "The New Hacker's Dictionary," a well-known compilation of hacker slang and culture.
-
B.
TN
TN is a UK postcode area covering Tunbridge Wells and surrounding parts of Kent and East Sussex.
-
C.
TN
TN is the official two-letter U.S. Postal Service abbreviation for the state of Tennessee.
-
D.
TN
TN is the official vehicle registration code used for the Indian state of Tamil Nadu.
-
E.
DNH
DNH is the abbreviated name for the Department of National Heritage, a government body responsible for preserving and promoting a nation's cultural and historical assets.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604ac0288190b59344bced8ac733 |
completed | April 1, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf896382708190a08c6bacf1157066 |
completed | April 3, 2026, 9:33 a.m. |
Created at: March 30, 2026, 6:47 p.m.