Triple
T25372272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux /proc file system |
E632960
|
entity |
| Predicate | mountPointDefault |
P158475
|
FINISHED |
| Object | /proc |
—
|
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: /proc | Statement: [Linux /proc file system, mountPointDefault, /proc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountPointDefault Context triple: [Linux /proc file system, mountPointDefault, /proc]
-
A.
mountOption
Indicates that a particular configuration option is applied when mounting a filesystem, device, or resource.
-
B.
mountOptionOf
Indicates that a specified mount option is associated with, or applies to, a particular filesystem mount.
-
C.
mountSystem
Indicates attaching a filesystem or storage resource to a system so that it becomes accessible for use.
-
D.
mountOrigin
Indicates the original source or location from which something is mounted or attached.
-
E.
mountType
Indicates the manner or configuration in which one object is mounted or attached to another.
- F. None of above. chosen
Provenance (4 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_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:38 p.m.