Triple
T28610318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel documentation |
E724152
|
entity |
| Predicate | directoryPath |
P94143
|
FINISHED |
| Object | Documentation/ |
—
|
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: Documentation/ | Statement: [Linux kernel documentation, directoryPath, Documentation/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directoryPath Context triple: [Linux kernel documentation, directoryPath, Documentation/]
-
A.
repositoryDirectoryName
Indicates the name assigned to the directory in which a repository is stored or organized.
-
B.
filePath
chosen
Indicates the relationship that specifies the location or directory path where a file is stored in a file system.
-
C.
pathTo
Indicates that one entity serves as a route, way, or means of reaching, accessing, or moving to another entity.
-
D.
defaultPath
Indicates that one path among several alternatives is designated as the standard or automatically chosen route in the absence of an explicit selection.
-
E.
namespacePath
Indicates the hierarchical namespace location or route that defines where an entity is organized within a structured naming 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 4:29 a.m.