Triple
T8247326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian Bug Tracking System |
E192879
|
entity |
| Predicate | bugSeverity |
P17287
|
FINISHED |
| Object | critical |
—
|
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: critical | Statement: [Debian Bug Tracking System, bugSeverity, critical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bugSeverity Context triple: [Debian Bug Tracking System, bugSeverity, critical]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
-
C.
issueType
chosen
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
D.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
E.
fastSeverity
Indicates the level or intensity of severity associated with something that is fast or time-critical.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7875318c819095f971ba513c54fd |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.