Triple

T35422588
Position Surface form Disambiguated ID Type / Status
Subject Tubular E1023832 entity
Predicate checkpointAvailability P182955 FINISHED
Object no mid-level checkpoint 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: no mid-level checkpoint | Statement: [Tubular, checkpointAvailability, no mid-level checkpoint]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: checkpointAvailability
Context triple: [Tubular, checkpointAvailability, no mid-level checkpoint]
  • A. hasCheckpointStatus
    Indicates that an entity is associated with a particular checkpoint and its current status within a process or workflow.
  • B. hasCheckpointInfrastructure
    Indicates that an entity possesses or is equipped with the necessary facilities, systems, or structures to support checkpoint operations.
  • C. hasCheckpoint
    Indicates that an entity includes, contains, or is associated with one or more intermediate control or verification points within its structure, process, or path.
  • D. checkpointManagedBy
    Indicates that the operation, control, or oversight of a checkpoint is carried out by a specified managing entity.
  • E. hasCheckpointControl
    Indicates that one entity exercises control, management, or authority over a checkpoint associated with another entity.
  • 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_69f76df6704081909900c60be10d5849 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7958d59388190a937ac6f4c81d3c9 completed May 3, 2026, 6:35 p.m.
PD Predicate disambiguation batch_69f7910770108190bdd39ddb5d304f54 completed May 3, 2026, 6:16 p.m.
PDg Predicate description generation batch_69f791cad5e08190a8a04ca283dbecaa completed May 3, 2026, 6:19 p.m.
Created at: May 3, 2026, 4:03 p.m.