Triple
T26317748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nroff |
E662017
|
entity |
| Predicate | usesEscapeCharacter |
P105360
|
FINISHED |
| Object | \ |
—
|
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: \ | Statement: [nroff, usesEscapeCharacter, \]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEscapeCharacter Context triple: [nroff, usesEscapeCharacter, \]
-
A.
supportsEscapeSequences
chosen
Indicates that an entity can recognize and correctly process escape sequence characters within its input or content.
-
B.
escapeOf
Indicates that one entity escapes, is released, or leaks out from another entity or containing context.
-
C.
escapesWith
Indicates that one entity flees or breaks free from a situation, place, or constraint together with another entity as a companion or accomplice.
-
D.
defaultEscaping
Indicates that a value, expression, or output is automatically transformed (escaped) into a safe representation by default to prevent unintended interpretation or execution.
-
E.
escapedTo
Indicates that an entity fled or broke free from a place, situation, or captor and reached another location as a result.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f28e9588190b76581e150f4f27d |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:26 p.m.