Triple
T18178382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PyMC3 |
E435219
|
entity |
| Predicate | supportsComputation |
P13868
|
FINISHED |
| Object | CPU |
—
|
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: CPU | Statement: [PyMC3, supportsComputation, CPU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsComputation Context triple: [PyMC3, supportsComputation, CPU]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving another entity.
-
C.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
D.
computationInput
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
-
E.
supportsOperationsIn
chosen
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df5b68f081908aac8210270f1499 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.