Triple
T28506904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | security.debian.org |
E721384
|
entity |
| Predicate | availabilityGoal |
P164599
|
FINISHED |
| Object | high availability |
—
|
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: high availability | Statement: [security.debian.org, availabilityGoal, high availability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availabilityGoal Context triple: [security.debian.org, availabilityGoal, high availability]
-
A.
availabilityTarget
Indicates that something is the intended object, resource, or condition whose availability is being specified, monitored, or constrained.
-
B.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
C.
availabilityPattern
Indicates a recurring schedule or pattern that defines when something is available or unavailable over time.
-
D.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
E.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:09 a.m.