Triple
T27736086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParameterizedThreadStart |
E697531
|
entity |
| Predicate | supportsPassing |
P93432
|
FINISHED |
| Object | single object parameter to thread method |
—
|
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: single object parameter to thread method | Statement: [ParameterizedThreadStart, supportsPassing, single object parameter to thread method]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPassing Context triple: [ParameterizedThreadStart, supportsPassing, single object parameter to thread method]
-
A.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
B.
supportsPassthrough
Indicates that one entity enables or allows another entity’s data, signals, or operations to pass through it unchanged.
-
C.
allowsStatePassing
Indicates that one entity permits another to transfer or maintain state information across interactions or components.
-
D.
canBePassedTo
chosen
Indicates that one entity is capable of being transferred, handed over, or given to another entity.
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: April 27, 2026, 3:12 p.m.