Triple
T12738992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU coding standards |
E304438
|
entity |
| Predicate | recommendsCommentStyle |
P102846
|
FINISHED |
| Object | clear and complete comments |
—
|
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: clear and complete comments | Statement: [GNU coding standards, recommendsCommentStyle, clear and complete comments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendsCommentStyle Context triple: [GNU coding standards, recommendsCommentStyle, clear and complete comments]
-
A.
supportsCommentsStyle
Indicates that one entity is capable of handling or displaying comments in a particular style or formatting convention.
-
B.
metaComment
Indicates that one statement or comment is about, analyzes, or provides commentary on another statement or comment.
-
C.
programmingStyle
Indicates the particular approach, methodology, or paradigm an entity uses when writing or organizing code.
-
D.
commentPolicy
chosen
Indicates that an entity defines rules or guidelines governing how comments may be created, displayed, or moderated in relation to another entity.
-
E.
supportsComments
Indicates that an entity allows or enables the addition, storage, or display of user comments associated with it.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.