Triple

T27736111
Position Surface form Disambiguated ID Type / Status
Subject ParameterizedThreadStart E697531 entity
Predicate invocationModel P39337 FINISHED
Object synchronous invocation on created thread 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: synchronous invocation on created thread | Statement: [ParameterizedThreadStart, invocationModel, synchronous invocation on created thread]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: invocationModel
Context triple: [ParameterizedThreadStart, invocationModel, synchronous invocation on created thread]
  • A. invocationType chosen
    Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
  • B. userInteractionModel
    Indicates how a user is expected to interact with a system, defining the style, rules, or pattern of those interactions.
  • C. executionModel
    Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
  • D. invocationOf
    Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
  • E. modelingClient
    Indicates that one entity serves as a client that is being modeled or represented by another entity in a modeling context.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f636a088b8819081e34d416b28cdac completed May 2, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 3:12 p.m.