Triple

T31582742
Position Surface form Disambiguated ID Type / Status
Subject VT52 E805868 entity
Predicate supportsInsertDeleteLine GENERATED
Object model-dependent UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsInsertDeleteLine
Context triple: [VT52, supportsInsertDeleteLine, model-dependent]
  • A. supportsLine
    Indicates that one entity provides structural, functional, or conceptual backing or reinforcement to a particular line (such as a line of text, code, argument, or physical alignment).
  • B. lineReplaced
    Indicates that one line has been substituted or superseded by another line, typically in a versioning, editing, or modification context.
  • C. supportsBackspaceOverstrike
    Indicates that an entity allows the use of backspace characters to overstrike and modify previously printed or displayed characters.
  • D. interchangeWithLine
    Indicates that one entity can be transferred or switched to another specific line, such as a route, track, or service line, at a given point.
  • E. supportsBadLines
    Indicates that one entity is capable of handling, accepting, or operating correctly even when provided with malformed, invalid, or otherwise “bad” lines of input or data.
  • F. None of above. chosen

Provenance (1 batch)

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.
Created at: April 30, 2026, 10:24 p.m.