Triple
T1887592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Hacker's Dictionary |
E41796
|
entity |
| Predicate | notableEditionYear |
P33056
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [The New Hacker's Dictionary, notableEditionYear, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEditionYear Context triple: [The New Hacker's Dictionary, notableEditionYear, 1993]
-
A.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
B.
anniversaryEditionPublicationYear
Indicates the year in which an anniversary edition of a work was published.
-
C.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
D.
notableDepictionYear
Indicates the year in which a notable or significant depiction of an entity occurred or was created.
-
E.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
- F. None of above. chosen
Provenance (4 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb121a3cc81909c60ac65627142d1 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.