Triple
T314730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora Linux |
E7681
|
entity |
| Predicate | previousPackageManager |
P9736
|
FINISHED |
| Object | YUM |
—
|
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: YUM | Statement: [Fedora Linux, previousPackageManager, YUM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPackageManager Context triple: [Fedora Linux, previousPackageManager, YUM]
-
A.
previousFileSystem
Indicates that one file system existed or was in use before another file system in a temporal or versioning sequence.
-
B.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
C.
previousVersionLocationOfAdoption
Indicates that one entity is the location where an earlier or prior version of another entity was adopted.
-
D.
predecessorSystem
chosen
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
E.
preinstalledOn
Indicates that a software or component comes already installed and ready to use on a particular device or system before the user receives it.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea62f830819089e94b3aa3e4e187 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.