Triple
T36872251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParamSpec |
E911253
|
entity |
| Predicate | backportedInModule |
P178946
|
FINISHED |
| Object | typing_extensions |
—
|
NE NERFINISHED |
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: typing_extensions | Statement: [ParamSpec, backportedInModule, typing_extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backportedInModule Context triple: [ParamSpec, backportedInModule, typing_extensions]
-
A.
backportedBy
Indicates that a change, fix, or feature has been taken from a newer version and applied to an older version by the referenced entity.
-
B.
backportedTo
Indicates that a change, feature, or fix originally made in a newer version has been applied retroactively to an older version.
-
C.
backportAvailableFor
Indicates that a change, feature, or fix has been made available as a backport for a specified earlier version or branch.
-
D.
backportLocation
chosen
Indicates the location or context to which a change, fix, or feature is backported from its original source.
-
E.
backwardCompatibleWith
Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.