Triple
T816080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PyPy |
E17653
|
entity |
| Predicate | hasReleaseType |
P3286
|
FINISHED |
| Object | stable releases |
—
|
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: stable releases | Statement: [PyPy, hasReleaseType, stable releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseType Context triple: [PyPy, hasReleaseType, stable releases]
-
A.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
B.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
C.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5157b08190b6c8f2fd455f261e |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.