Triple
T17559851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pkg |
E427670
|
entity |
| Predicate | databaseLocation |
P9488
|
FINISHED |
| Object | /var/db/pkg |
—
|
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: /var/db/pkg | Statement: [pkg, databaseLocation, /var/db/pkg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: databaseLocation Context triple: [pkg, databaseLocation, /var/db/pkg]
-
A.
repositoryLocation
chosen
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
B.
baseLocation
Indicates the primary place where an entity is based, headquartered, or operates from as its main location.
-
C.
deploymentLocation
Indicates the place or environment where something (such as a system, resource, or component) is deployed or put into operational use.
-
D.
encryptionLocation
Indicates the place or environment where an encryption process is performed or applied.
-
E.
dataCollectionLocation
Indicates the place or setting where data is gathered, recorded, or measured.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562573e48190a19f30fe915a5455 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.