Triple

T7568184
Position Surface form Disambiguated ID Type / Status
Subject Karpinsky Group Volcano E178972 entity
Predicate monitoringStatus P70758 FINISHED
Object limited monitoring 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: limited monitoring | Statement: [Karpinsky Group Volcano, monitoringStatus, limited monitoring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: monitoringStatus
Context triple: [Karpinsky Group Volcano, monitoringStatus, limited monitoring]
  • A. monitoringOutput
    Indicates that one entity observes, records, or tracks the performance, behavior, or results produced by another entity or process.
  • B. monitoringBody
    Indicates that one entity is responsible for overseeing, supervising, or tracking the activities, performance, or compliance of another entity.
  • C. isMonitored chosen
    Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
  • D. automationStatus
    Indicates whether a process, task, or system is being performed automatically or requires manual intervention.
  • E. maintenanceStatus
    Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
  • 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_69c69f2f80288190b95cceb4da92ab2b completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f91d9bfc8190af6f5f8211c3dda2 completed March 27, 2026, 9:39 p.m.
PD Predicate disambiguation batch_69c6f4dc485c819080da13e3b7f4f08f completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:51 p.m.