Triple
T29408608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portage |
E745836
|
entity |
| Predicate | distfilesLocation |
P166752
|
FINISHED |
| Object | /var/cache/distfiles |
—
|
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/cache/distfiles | Statement: [Portage, distfilesLocation, /var/cache/distfiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distfilesLocation Context triple: [Portage, distfilesLocation, /var/cache/distfiles]
-
A.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
B.
deploymentLocation
Indicates the place or environment where something (such as a system, resource, or component) is deployed or put into operational use.
-
C.
documentationLocation
Indicates the place or resource where relevant documentation for an entity can be found.
-
D.
binaryLocation
Indicates that one entity is the physical or logical location where another binary or executable artifact resides.
-
E.
metadataLocation
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a35eeb48190872f62f2e455ffee |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:55 p.m.