Triple
T27736113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParameterizedThreadStart |
E697531
|
entity |
| Predicate | threadAssociation |
P150505
|
FINISHED |
| Object | used when constructing a Thread instance |
—
|
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: used when constructing a Thread instance | Statement: [ParameterizedThreadStart, threadAssociation, used when constructing a Thread instance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threadAssociation Context triple: [ParameterizedThreadStart, threadAssociation, used when constructing a Thread instance]
-
A.
threadAffinity
Indicates that an operation, task, or resource is bound to execute on a specific thread or set of threads.
-
B.
threadContext
Indicates that one entity functions as the contextual or conversational environment within which the other entity (such as a message, action, or event) occurs or is interpreted.
-
C.
threadBehavior
Indicates how a thread operates or responds under certain conditions within a concurrent or multi-threaded context.
-
D.
threadConstruction
chosen
Indicates the process or method by which a thread (e.g., in textiles or computing) is created, structured, or set up.
-
E.
associatedCurrent
Indicates a relationship where a particular current is linked or connected to another entity as its relevant or corresponding current.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 3:12 p.m.