Triple
T14342842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | javadoc |
E355644
|
entity |
| Predicate | usesCommentStyle |
P85210
|
FINISHED |
| Object | Javadoc 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: Javadoc comments | Statement: [javadoc, usesCommentStyle, Javadoc comments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommentStyle Context triple: [javadoc, usesCommentStyle, Javadoc comments]
-
A.
supportsCommentsStyle
chosen
Indicates that one entity is capable of handling or displaying comments in a particular style or formatting convention.
-
B.
supportsComments
Indicates that an entity allows or enables the addition, storage, or display of user comments associated with it.
-
C.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
-
D.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
E.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e87febc8190a63c668cbd0fd713 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.