Triple
T31582726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VT52 |
E805868
|
entity |
| Predicate | controlCodeStyle |
P192055
|
FINISHED |
| Object | VT52 escape sequences |
—
|
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: VT52 escape sequences | Statement: [VT52, controlCodeStyle, VT52 escape sequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlCodeStyle Context triple: [VT52, controlCodeStyle, VT52 escape sequences]
-
A.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
B.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
C.
programmingStyle
Indicates the particular approach, methodology, or paradigm an entity uses when writing or organizing code.
-
D.
controlCodes
chosen
Indicates that one entity possesses or defines codes or signals used to control, configure, or command the behavior of another entity.
-
E.
codeStandardization
Indicates that multiple pieces of code are being aligned to a common format, style, or set of conventions to ensure consistency.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 30, 2026, 10:24 p.m.