Triple
T1724385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpine Linux |
E37463
|
entity |
| Predicate | sourceRepository |
P9488
|
FINISHED |
| Object | https://git.alpinelinux.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: https://git.alpinelinux.org/ | Statement: [Alpine Linux, sourceRepository, https://git.alpinelinux.org/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceRepository Context triple: [Alpine Linux, sourceRepository, https://git.alpinelinux.org/]
-
A.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
B.
repositoryLocation
chosen
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
C.
deploymentSource
Indicates the origin or mechanism from which something is deployed, such as the system, process, or source responsible for initiating the deployment.
-
D.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
-
E.
sourceState
Indicates the original or starting state from which a transition, change, or process begins.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.