Triple
T4278041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pip |
E97086
|
entity |
| Predicate | stableReleaseStatus |
P55170
|
FINISHED |
| Object | stable |
—
|
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 | Statement: [pip, stableReleaseStatus, stable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableReleaseStatus Context triple: [pip, stableReleaseStatus, stable]
-
A.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
B.
stableReleasesMaintainedBy
Indicates that the stable (non-development) releases of a software project are currently being maintained or supported by a particular entity.
-
C.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
D.
originalReleaseStatus
Indicates the publication or distribution state of a work at the time of its initial release.
-
E.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350201ac88190b9d8980da5f0d03d |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.