Triple
T28506715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian backports |
E721380
|
entity |
| Predicate | versioningRule |
P164861
|
FINISHED |
| Object | backported packages use higher version numbers than 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: backported packages use higher version numbers than stable | Statement: [Debian backports, versioningRule, backported packages use higher version numbers than stable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: versioningRule Context triple: [Debian backports, versioningRule, backported packages use higher version numbers than stable]
-
A.
versioningModel
Indicates that one entity serves as a versioning or revision-control model governing how versions of another entity are created, tracked, and managed.
-
B.
versionedAs
Indicates that one entity exists as a specific version or revision of another entity.
-
C.
versionField
Indicates that one entity serves as the version identifier or version-tracking field associated with another entity.
-
D.
versionFormat
Indicates the specific structural pattern or notation used to represent a version identifier.
-
E.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 3:09 a.m.