Triple
T25556047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0-13-110362-8 |
E640569
|
entity |
| Predicate | hasCoverAuthorsOrder |
P160091
|
FINISHED |
| Object | Brian W. Kernighan; Dennis M. Ritchie |
—
|
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: Brian W. Kernighan; Dennis M. Ritchie | Statement: [0-13-110362-8, hasCoverAuthorsOrder, Brian W. Kernighan; Dennis M. Ritchie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverAuthorsOrder Context triple: [0-13-110362-8, hasCoverAuthorsOrder, Brian W. Kernighan; Dennis M. Ritchie]
-
A.
hasAuthorNameOnCover
Indicates that the name of the author is printed or displayed on the cover of the work.
-
B.
authorOrder
chosen
Indicates the sequence or ranking of authors associated with a work, specifying each author's position in the authorship list.
-
C.
hasAuthorityOnCover
Indicates that one entity holds decision-making or control authority over the content, design, or use of another entity’s cover (e.g., a document, publication, or product).
-
D.
isCoverOf
Indicates that one entity functions as a protective or enclosing layer placed over another entity.
-
E.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
- F. None of above.
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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 21, 2026, 3:39 p.m.