Triple
T29698540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dconf |
E751417
|
entity |
| Predicate | typicalPathPrefix |
—
|
GENERATED |
| Object | /org/gnome/ |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPathPrefix Context triple: [dconf, typicalPathPrefix, /org/gnome/]
-
A.
registryPathPrefix
Indicates that one entity specifies the leading portion of a registry path under which the other entity’s registry keys or values are located.
-
B.
defaultPath
Indicates that one path among several alternatives is designated as the standard or automatically chosen route in the absence of an explicit selection.
-
C.
standardPrefix
chosen
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
D.
namespacePath
Indicates the hierarchical namespace location or route that defines where an entity is organized within a structured naming system.
-
E.
regionPrefix
Indicates that one region’s identifier or code serves as the starting substring (prefix) of another region’s identifier or code, expressing a hierarchical or nested regional relationship.
- F. None of above.
Provenance (1 batch)
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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:22 p.m.