Triple
T29689527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gNewSense |
E751176
|
entity |
| Predicate | softwareRepositoryPolicy |
P167597
|
FINISHED |
| Object | no non-free repositories enabled |
—
|
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: no non-free repositories enabled | Statement: [gNewSense, softwareRepositoryPolicy, no non-free repositories enabled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareRepositoryPolicy Context triple: [gNewSense, softwareRepositoryPolicy, no non-free repositories enabled]
-
A.
softwareRepository
Indicates that one entity serves as a software code repository or storage location for another entity’s software artifacts or projects.
-
B.
softwarePolicy
Indicates that there is a rule, guideline, or policy governing the use, development, or management of software in relation to the associated entities.
-
C.
repositoryPolicy
chosen
Indicates that a specified policy governs how a repository is configured, managed, or accessed.
-
D.
softwareLibrary
Indicates that one entity is a software library that provides code, functionality, or services used by another entity.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672938e18819082394196f97e6340 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:15 p.m.