Triple
T7089796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The C Programming Language |
E165161
|
entity |
| Predicate | firstEditionISBN |
P74471
|
FINISHED |
| Object | 0-13-110163-3 |
—
|
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: 0-13-110163-3 | Statement: [The C Programming Language, firstEditionISBN, 0-13-110163-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionISBN Context triple: [The C Programming Language, firstEditionISBN, 0-13-110163-3]
-
A.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
-
B.
firstEditionCategory
Indicates that an item belongs to a category specifically defined for its first edition.
-
C.
firstEditionPublicationYear
Indicates the year in which an entity’s first edition was originally published.
-
D.
firstEditionResult
Indicates that one entity is the outcome, record, or result associated specifically with the first edition of another entity.
-
E.
isbnFirstEnglishEdition
Indicates that the object is the ISBN identifier corresponding to the first English-language edition of the subject work.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e52ec0348190ac090c2fee3edfb8 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:41 p.m.