Triple
T25960383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The AWK Programming Language |
E645519
|
entity |
| Predicate | coAuthorOfLanguage |
P159602
|
FINISHED |
| Object | Brian W. Kernighan |
—
|
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 | Statement: [The AWK Programming Language, coAuthorOfLanguage, Brian W. Kernighan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthorOfLanguage Context triple: [The AWK Programming Language, coAuthorOfLanguage, Brian W. Kernighan]
-
A.
coAuthorOfLanguage
chosen
Indicates that two or more entities jointly authored, designed, or created a particular language.
-
B.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
C.
languageAuthor
Indicates that an entity is the creator or originator of a particular language.
-
D.
creatorLanguage
Indicates the language in which the creator produced or expressed the related work or content.
-
E.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c60fe0819092ad09d1c5b0c100 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:47 a.m.