Triple
T17557247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 420 |
E427619
|
entity |
| Predicate | requiresPythonVersionAtLeast |
P33702
|
FINISHED |
| Object | 3.3 |
—
|
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.3 | Statement: [PEP 420, requiresPythonVersionAtLeast, 3.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPythonVersionAtLeast Context triple: [PEP 420, requiresPythonVersionAtLeast, 3.3]
-
A.
requiresClientVersionAtLeast
Indicates that performing this action or relationship is only valid if the client's version is greater than or equal to a specified minimum version.
-
B.
requiresServerVersionAtLeast
Indicates that performing this action or relationship is only valid if the server’s version is greater than or equal to a specified minimum version.
-
C.
requiresLanguageVersion
chosen
Indicates that one entity depends on or must use a specific version of a language in order to function or be considered valid.
-
D.
requiresCompatibilityWith
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
E.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562413d08190acaa5272046d3626 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.