Triple

T17677745
Position Surface form Disambiguated ID Type / Status
Subject std::thread::spawn E440681 entity
Predicate executesConcurrentlyWith P47102 FINISHED
Object current 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: current thread | Statement: [std::thread::spawn, executesConcurrentlyWith, current thread]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: executesConcurrentlyWith
Context triple: [std::thread::spawn, executesConcurrentlyWith, current thread]
  • A. executedAlongWith
    Indicates that one entity was carried out, performed, or implemented in conjunction with another entity, at the same time or as part of the same operation or event.
  • B. heldConcurrentlyWith chosen
    Indicates that two or more events, roles, or states occurred or were in effect at the same time.
  • C. organizedInParallelWith
    Indicates that one process, event, or activity is arranged or carried out at the same time and in coordination with another, rather than sequentially.
  • D. isMostlyConcurrentWith
    Indicates that two events or intervals overlap in time for the majority of their durations, though not necessarily starting or ending together.
  • E. partlyConcurrentWith
    Indicates that two events or intervals overlap in time for some, but not all, of their durations.
  • 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6e959c819092d9d33e79bd51f7 completed April 19, 2026, 6 a.m.
PD Predicate disambiguation batch_69e3cde3673c8190a889e14ba1f07dc1 completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 10:01 a.m.