Triple
T17677774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | std::thread::spawn |
E440681
|
entity |
| Predicate | commonPattern |
P7254
|
FINISHED |
| Object | move closures capturing data by value |
—
|
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: move closures capturing data by value | Statement: [std::thread::spawn, commonPattern, move closures capturing data by value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPattern Context triple: [std::thread::spawn, commonPattern, move closures capturing data by value]
-
A.
commonStructure
Indicates that two or more entities share the same or a very similar internal organization, pattern, or arrangement.
-
B.
usagePattern
Indicates how something is typically used or the recurring manner in which it is employed or consumed.
-
C.
commonIn
chosen
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
E.
famousPattern
Indicates that one entity is widely recognized or renowned for a particular style, design, or recurring configuration associated with 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_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.