Triple

T32498217
Position Surface form Disambiguated ID Type / Status
Subject Universal Composability framework E830582 entity
Predicate capturesScenario P57928 FINISHED
Object concurrent protocol executions 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: concurrent protocol executions | Statement: [Universal Composability framework, capturesScenario, concurrent protocol executions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: capturesScenario
Context triple: [Universal Composability framework, capturesScenario, concurrent protocol executions]
  • A. scenarioType
    Indicates the specific category or kind of situation, context, or use case that an entity or event is associated with.
  • B. snapSituation
    Indicates a situation or context in which a sudden, decisive, or snapshot-like event or state occurs between entities.
  • C. scenes
    Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
  • D. captureCondition
    Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
  • E. capturesPhenomenon chosen
    Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
  • 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_69f349219cb8819087e120f509629c1b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c4409dc48190a9eac031b88571a1 completed May 3, 2026, 3:42 a.m.
PD Predicate disambiguation batch_69f6bd25bed08190befcabd3a41ffadf completed May 3, 2026, 3:12 a.m.
Created at: May 1, 2026, 12:59 a.m.