Triple
T28421727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian contrib component |
E719956
|
entity |
| Predicate | archiveSectionOf |
P3120
|
FINISHED |
| Object | Debian stable |
—
|
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: Debian stable | Statement: [Debian contrib component, archiveSectionOf, Debian stable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archiveSectionOf Context triple: [Debian contrib component, archiveSectionOf, Debian stable]
-
A.
collectionSection
Indicates a relationship where a collection is divided into or associated with a specific section or subdivision within it.
-
B.
archivesModel
Indicates that one entity stores and preserves another entity as an archived model for long-term reference or retrieval.
-
C.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
D.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
E.
archiveContent
Indicates that content is being stored or moved into an archive state for long-term retention or historical reference.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 1:34 a.m.