Triple
T27586434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | libdnf |
E699699
|
entity |
| Predicate | usedInDistribution |
P79897
|
FINISHED |
| Object | Fedora |
—
|
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: Fedora | Statement: [libdnf, usedInDistribution, Fedora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDistribution Context triple: [libdnf, usedInDistribution, Fedora]
-
A.
usedByDistribution
chosen
Indicates that something (such as a resource, component, or artifact) is utilized or consumed by a particular distribution.
-
B.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
allowsDistribution
Indicates that one entity grants permission for another entity to distribute or disseminate something (e.g., content, products, or data).
-
E.
usedInLibrary
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 2:04 p.m.