Triple
T13849373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1055 |
E332892
|
entity |
| Predicate | escapeCharacter |
P105360
|
FINISHED |
| Object | ESC (0xDB) |
—
|
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: ESC (0xDB) | Statement: [RFC 1055, escapeCharacter, ESC (0xDB)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeCharacter Context triple: [RFC 1055, escapeCharacter, ESC (0xDB)]
-
A.
defaultEscaping
Indicates that a value, expression, or output is automatically transformed (escaped) into a safe representation by default to prevent unintended interpretation or execution.
-
B.
escapedBy
Indicates that an entity is freed or enabled to escape through the actions or intervention of another entity.
-
C.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
D.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
-
E.
supportsEscapeSequences
chosen
Indicates that an entity can recognize and correctly process escape sequence characters within its input or content.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02d8fb788190baef7537be2baecb |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.