Triple
T26317738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nroff |
E662017
|
entity |
| Predicate | supportsBackspaceOverstrike |
P196169
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [nroff, supportsBackspaceOverstrike, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBackspaceOverstrike Context triple: [nroff, supportsBackspaceOverstrike, true]
-
A.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
B.
supportsEscapeSequences
Indicates that an entity can recognize and correctly process escape sequence characters within its input or content.
-
C.
supportsBackpressure
Indicates that the entity can handle and regulate backpressure, allowing it to slow or adjust data flow in response to downstream demand or capacity.
-
D.
supportsSplitKeyboard
Indicates that an entity is compatible with or provides functionality for using a split keyboard configuration.
-
E.
supportsSlideOver
Indicates that one entity enables or is compatible with displaying another entity in a slide-over (partially overlaid) interface or view.
- F. None of above. chosen
Provenance (4 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_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_69fe12a769c08190bc445d302d2e8f98 |
completed | May 8, 2026, 4:43 p.m. |
Created at: April 26, 2026, 10:26 p.m.