Triple
T1724489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ext4 |
E37465
|
entity |
| Predicate | defaultFileSystemOn |
P10381
|
FINISHED |
| Object | many Linux distributions |
—
|
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: many Linux distributions | Statement: [ext4, defaultFileSystemOn, many Linux distributions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultFileSystemOn Context triple: [ext4, defaultFileSystemOn, many Linux distributions]
-
A.
defaultFileSystem
chosen
Indicates that a given file system is the primary or standard file system automatically used by default for file operations in a particular context.
-
B.
previousFileSystem
Indicates that one file system existed or was in use before another file system in a temporal or versioning sequence.
-
C.
defaultConfigFile
Indicates that a given file is designated as the default configuration file used when no other configuration is explicitly specified.
-
D.
defaultBrowserOn
Indicates that a particular browser is set as the default browser on a given device or system.
-
E.
currentSystem
Indicates that an entity is the system or configuration that is presently active or in use.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.