Triple
T36872250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParamSpec |
E911253
|
entity |
| Predicate | availableFromPythonVersion |
P11235
|
FINISHED |
| Object | 3.10 |
—
|
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: 3.10 | Statement: [ParamSpec, availableFromPythonVersion, 3.10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableFromPythonVersion Context triple: [ParamSpec, availableFromPythonVersion, 3.10]
-
A.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
B.
introducedVersionOf
Indicates that one entity is the version in which another entity was first introduced or made available.
-
C.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
D.
usedInVersionRange
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
E.
introducedWithVersion
chosen
Indicates that something first became available or was added starting from a specific version.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.