Triple
T28506702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian backports |
E721380
|
entity |
| Predicate | urlPattern |
P49348
|
FINISHED |
| Object | deb http://deb.debian.org/debian <stable>-backports main |
—
|
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: deb http://deb.debian.org/debian <stable>-backports main | Statement: [Debian backports, urlPattern, deb http://deb.debian.org/debian <stable>-backports main]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urlPattern Context triple: [Debian backports, urlPattern, deb http://deb.debian.org/debian <stable>-backports main]
-
A.
URLPattern
chosen
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
-
B.
locationPattern
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
-
C.
dstRulePattern
Indicates a rule-based pattern that specifies or constrains the characteristics of a destination in a relationship or process.
-
D.
languagePattern
Indicates a recurring or structured way in which language is used, organized, or formed within a given context.
-
E.
auxiliaryRoutePattern
Indicates that one route serves as an auxiliary or supplemental path that follows or branches from a primary route according to a specific pattern or configuration.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f72071081909b841e702846a33b |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:09 a.m.