Triple
T10167978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenVPN |
E235253
|
entity |
| Predicate | hasConfigurationFileExtension |
P49341
|
FINISHED |
| Object | .ovpn |
—
|
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: .ovpn | Statement: [OpenVPN, hasConfigurationFileExtension, .ovpn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConfigurationFileExtension Context triple: [OpenVPN, hasConfigurationFileExtension, .ovpn]
-
A.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
B.
hasFileExtension
Indicates that one entity (typically a file) possesses a specific file extension denoting its type or format.
-
C.
hasProjectFileExtension
Indicates that a project is associated with or saved using a specific file extension.
-
D.
configurationFileExtension
chosen
Indicates the file extension used for a configuration file associated with an entity.
-
E.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6f64a48190883aefce58a65ca6 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.