Triple
T28421751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian contrib component |
E719956
|
entity |
| Predicate | hasRepositoryURL |
P89567
|
FINISHED |
| Object | http://deb.debian.org/debian |
—
|
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: http://deb.debian.org/debian | Statement: [Debian contrib component, hasRepositoryURL, http://deb.debian.org/debian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepositoryURL Context triple: [Debian contrib component, hasRepositoryURL, http://deb.debian.org/debian]
-
A.
hasRepository
Indicates that an entity maintains or is associated with a specific repository (such as a code, data, or content store).
-
B.
repositoryUrl
chosen
Indicates the web address where the related code, data, or resources are stored and managed in a version-controlled repository.
-
C.
hasPackageRepository
Indicates that an entity is associated with or provides access to a specific software package repository.
-
D.
hasRepositoryMirror
Indicates that one repository serves as a mirrored copy or synchronized duplicate of another repository.
-
E.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
- 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_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 28, 2026, 1:34 a.m.