Triple
T34442450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Python 3.9 |
E884131
|
entity |
| Predicate | standardLibraryVersion |
P191118
|
FINISHED |
| Object | Python 3.9 standard library |
—
|
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: Python 3.9 standard library | Statement: [Python 3.9, standardLibraryVersion, Python 3.9 standard library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardLibraryVersion Context triple: [Python 3.9, standardLibraryVersion, Python 3.9 standard library]
-
A.
standardEditionVolume
Indicates that one entity is a volume that forms part of a standard edition of another entity (such as a work or collection).
-
B.
hasStandardVersion
Indicates that one entity serves as the official or canonical version of another entity.
-
C.
coreVersionOf
Indicates that one entity is the fundamental or base version from which another related variant or derivative is formed.
-
D.
standardVersionEditor
Indicates that an entity serves as the editor responsible for preparing or maintaining a particular standard version.
-
E.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 1, 2026, 2 a.m.