Triple
T34442514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 647 TypeGuard |
E884133
|
entity |
| Predicate | backportLocation |
P178946
|
FINISHED |
| Object | typing_extensions.TypeGuard |
—
|
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: typing_extensions.TypeGuard | Statement: [PEP 647 TypeGuard, backportLocation, typing_extensions.TypeGuard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backportLocation Context triple: [PEP 647 TypeGuard, backportLocation, typing_extensions.TypeGuard]
-
A.
backportAvailableFor
Indicates that a change, feature, or fix has been made available as a backport for a specified earlier version or branch.
-
B.
backportedTo
Indicates that a change, feature, or fix originally made in a newer version has been applied retroactively to an older version.
-
C.
binaryLocation
Indicates that one entity is the physical or logical location where another binary or executable artifact resides.
-
D.
branchLocation
Indicates the physical or geographical location where a particular branch of an organization or structure is situated.
-
E.
builderLocation
Indicates the place or area where the builder carries out their building activity or is based.
- F. None of above. chosen
Provenance (4 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.