Triple
T7987498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2119 |
E185717
|
entity |
| Predicate | keywordStyle |
P25612
|
FINISHED |
| Object | uppercase key words |
—
|
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: uppercase key words | Statement: [RFC 2119, keywordStyle, uppercase key words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keywordStyle Context triple: [RFC 2119, keywordStyle, uppercase key words]
-
A.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
B.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
-
C.
syntaxStyle
chosen
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
D.
editingStyle
Indicates the characteristic manner or approach used when revising, arranging, or refining content.
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4d11b08190aa13afb17155462c |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.