Triple
T29406956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zypper |
E745798
|
entity |
| Predicate | defaultRepositoryFormat |
P180436
|
FINISHED |
| Object | RPM-MD |
—
|
NE NERFINISHED |
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: RPM-MD | Statement: [zypper, defaultRepositoryFormat, RPM-MD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultRepositoryFormat Context triple: [zypper, defaultRepositoryFormat, RPM-MD]
-
A.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
-
B.
registryFormat
Indicates that one entity specifies the data format or schema used for registering another entity in a registry.
-
C.
defaultVolumeFormat
Indicates the standard or preselected format in which a volume is created, stored, or presented unless an alternative is specified.
-
D.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
E.
containerFormats
Indicates that one entity serves as a container or packaging format used to hold, encapsulate, or structure the contents of another entity.
- 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 28, 2026, 2:54 p.m.