Triple
T27735727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadLocal<T> |
E697522
|
entity |
| Predicate | notThreadSafeFor |
P114207
|
FINISHED |
| Object | sharing Value across threads |
—
|
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: sharing Value across threads | Statement: [ThreadLocal<T>, notThreadSafeFor, sharing Value across threads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notThreadSafeFor Context triple: [ThreadLocal<T>, notThreadSafeFor, sharing Value across threads]
-
A.
threadSafe
Indicates that an operation or relationship can be safely executed concurrently by multiple threads without causing data races or inconsistent state.
-
B.
isThreadSafeValueType
Indicates that a value type can be safely accessed and modified by multiple threads concurrently without causing data races or inconsistent state.
-
C.
supportsMultithreading
Indicates that the subject is capable of executing multiple threads concurrently within the same process.
-
D.
notWellDocumented
Indicates that the subject lacks sufficient, clear, or comprehensive documentation.
-
E.
notDesignedAs
chosen
Indicates that one entity was not created, intended, or purposed to serve as or function as the other entity.
- 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.