Triple
T37035415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 647 |
E916620
|
entity |
| Predicate | modifiesTypingBehavior |
P95862
|
FINISHED |
| Object | type checkers |
—
|
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: type checkers | Statement: [PEP 647, modifiesTypingBehavior, type checkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiesTypingBehavior Context triple: [PEP 647, modifiesTypingBehavior, type checkers]
-
A.
hasTypingFeature
chosen
Indicates that an entity possesses or supports a particular typing-related characteristic or capability.
-
B.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
-
C.
typingDiscipline
Indicates how a programming language enforces and manages type rules for its values and expressions.
-
D.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
E.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.