Triple
T28506559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian package archive |
E721377
|
entity |
| Predicate | hasSubArchive |
P192978
|
FINISHED |
| Object | security.debian.org |
—
|
NE NERFINISHED |
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: security.debian.org | Statement: [Debian package archive, hasSubArchive, security.debian.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubArchive Context triple: [Debian package archive, hasSubArchive, security.debian.org]
-
A.
hasSubvolume
Indicates that one volume is contained within or forms a distinct, defined part of another larger volume.
-
B.
hasSubproject
Indicates that a project includes another project as a subordinate or component part within its overall structure.
-
C.
hasSubSeries
Indicates that one series is a subordinate or component series within a larger parent series.
-
D.
hasSubArchitecture
Indicates that one architectural component or structure is a subordinate or constituent part of a larger overarching architecture.
-
E.
hasSubspace
Indicates that one space is a subset or component of another, existing entirely within the larger space.
- 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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: April 28, 2026, 3:09 a.m.