Triple
T34442527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 647 TypeGuard |
E884133
|
entity |
| Predicate | designDecision |
P157809
|
FINISHED |
| Object | TypeGuard is covariant in its type parameter |
—
|
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: TypeGuard is covariant in its type parameter | Statement: [PEP 647 TypeGuard, designDecision, TypeGuard is covariant in its type parameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designDecision Context triple: [PEP 647 TypeGuard, designDecision, TypeGuard is covariant in its type parameter]
-
A.
developmentDecision
Indicates a decision-making relationship in which an authority or stakeholder chooses a course of action or policy regarding the development or progression of something.
-
B.
designDecisionsInfluencedBy
chosen
Indicates that one entity’s design decisions are shaped, guided, or affected by another entity or factor.
-
C.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
D.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
decide
Indicates that an entity makes a choice or judgment between options or possible courses of action.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 2 a.m.