Triple

T29911828
Position Surface form Disambiguated ID Type / Status
Subject AVCaptureSession E759689 entity
Predicate hasNotification P173704 FINISHED
Object AVCaptureSessionDidStartRunningNotification 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: AVCaptureSessionDidStartRunningNotification | Statement: [AVCaptureSession, hasNotification, AVCaptureSessionDidStartRunningNotification]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotification
Context triple: [AVCaptureSession, hasNotification, AVCaptureSessionDidStartRunningNotification]
  • A. hasAnnouncement chosen
    Indicates that an entity issues, contains, or is associated with a specific announcement.
  • B. requiresNotification
    Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
  • C. requiresNotificationFrom
    Indicates that one entity must receive a notification from another entity before or when a certain condition, event, or action occurs.
  • D. requiresNotificationTo
    Indicates that one entity must send a notification to another entity before or when a certain condition, event, or action occurs.
  • E. hasNotableResponse
    Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
  • 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_69f224600590819085e148a01c056ef6 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_6a000014497c819088d5cda3977522dd completed May 10, 2026, 3:48 a.m.
PD Predicate disambiguation batch_69ffff9a52b08190be1024e0fb6fe661 completed May 10, 2026, 3:46 a.m.
Created at: April 29, 2026, 6:10 p.m.