Triple
T25372301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux /proc file system |
E632960
|
entity |
| Predicate | perProcessDirectoryContains |
P135881
|
FINISHED |
| Object | maps |
—
|
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: maps | Statement: [Linux /proc file system, perProcessDirectoryContains, maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perProcessDirectoryContains Context triple: [Linux /proc file system, perProcessDirectoryContains, maps]
-
A.
hasDirectoryStructureElement
chosen
Indicates that one entity is a component, segment, or node within the hierarchical structure of a directory associated with another entity.
-
B.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
-
C.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
D.
containsTest
Indicates that one entity includes or encompasses another entity as a test or testing component.
-
E.
processIncludes
Indicates that a process contains, encompasses, or incorporates another process or subprocess as part of its overall execution or structure.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:38 p.m.