Triple
T28506912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | security.debian.org |
E721384
|
entity |
| Predicate | relatedDomain |
P199711
|
FINISHED |
| Object | www.debian.org |
—
|
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: www.debian.org | Statement: [security.debian.org, relatedDomain, www.debian.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDomain Context triple: [security.debian.org, relatedDomain, www.debian.org]
-
A.
involvedDomain
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
-
B.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
D.
connectedDomain
chosen
Indicates that one domain is linked or associated with another domain in a meaningful or functional way.
-
E.
partOfDomain
Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
- 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_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 28, 2026, 3:09 a.m.