Triple
T27586453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | libdnf |
E699699
|
entity |
| Predicate | previouslyUsedBuildSystem |
P19952
|
FINISHED |
| Object | Autotools |
—
|
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: Autotools | Statement: [libdnf, previouslyUsedBuildSystem, Autotools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyUsedBuildSystem Context triple: [libdnf, previouslyUsedBuildSystem, Autotools]
-
A.
previouslyUsedSystem
Indicates that an entity made use of a particular system at some time in the past, prior to the current context or state.
-
B.
hasBuildTool
chosen
Indicates that an entity uses or is associated with a specific tool or system for building, compiling, or assembling software or other artifacts.
-
C.
builtAgainst
Indicates that one structure or object is constructed directly adjoining and supported by the side or surface of another.
-
D.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
E.
previouslySupportedVersionControlSystem
Indicates that an entity used to support a particular version control system in the past but no longer does so.
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 2:04 p.m.