Triple
T32416851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATL |
E828349
|
entity |
| Predicate | supportsThreadingModels |
P90876
|
FINISHED |
| Object | single-threaded |
—
|
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-threaded | Statement: [ATL, supportsThreadingModels, single-threaded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsThreadingModels Context triple: [ATL, supportsThreadingModels, single-threaded]
-
A.
supportsMultithreading
Indicates that the subject is capable of executing multiple threads concurrently within the same process.
-
B.
supportsParallelProgrammingModel
Indicates that one entity provides facilities or mechanisms enabling the use of a parallel programming model with another entity.
-
C.
threadingRequirement
Indicates the conditions or constraints under which an operation must be executed with respect to threads (e.g., which thread or threading model is required).
-
D.
supportsConcurrentModelExecution
Indicates that one entity enables or allows multiple models to be executed at the same time without mutual interference.
-
E.
threadingBehavior
chosen
Indicates how execution threads are managed or utilized in performing an operation or maintaining a process.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:54 a.m.